home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!mcsun!sun4nl!freya.let.rug.nl!welling
- From: welling@let.rug.nl (George Welling)
- Subject: Re: Foxpro and Insufficient Memory Errors
- Message-ID: <1993Jan8.144342.17459@let.rug.nl>
- Sender: news@let.rug.nl (news manager)
- Nntp-Posting-Host: tyr.let.rug.nl
- Organization: Faculteit der Letteren, Rijksuniversiteit Groningen, NL
- References: <1993Jan7.222734.20312@nntpd2.cxo.dec.com>
- Date: Fri, 8 Jan 1993 14:43:42 GMT
- Lines: 20
-
- In article <1993Jan7.222734.20312@nntpd2.cxo.dec.com> scott@talguy.cxo.dec.com (Scott Johnson) writes:
- >
- >Is there a command I can run ocassionally during the execution of the program
- >which will cut down and possibly reclaim unused memory? I was hoping there
- >was some sort of garbage collection routine that can be invoked once in a
- >while during the execution cycle of the application.
- > Scott Johnson
- > Digital Equipment Corporation
- > Colorado Springs, Co
- >
-
- I am not sure if this will solve the problem, but I have solved related
- problems by using the FLUSH command after every READ: this keeps the buffers
- as small as possible. You could also try SET AUTOSAVE ON (the default is OFF),
- this does about the same.
-
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- George M. Welling - dep.Alfa-Informatica HCI - University of Groningen
- phone : +31 50 63 54 74 | fax : +31 50 63 49 00 | welling@let.rug.nl
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-