>>>Would someone know of how to limit VFP5.0 apps from taking up enormous amounts of memory? What are some of the things I should be looking for, local vs. remote tables? Built in arrays instead of tables at all?
>>>
>>>I've been running a beta version of my software now for about 25 days and everything is going okay, except the application, after just starting up, gobbles up roughly 6 MB (according to the Win95 system monitor) of available system memory. I have 13 tables, all remotely loaded (3 containing 2000 to 3000 records) and 2 remote views.
>>>
>>>On my 32MB workstation this isn't much of a problem, but with the user's stations at 16MB each, that is stretching it.
>>>
>>>Is there somewhere in the docs that describe ways of trimming down memory "footprints"? If you have any suggestions it would be highly appreciated.
>>>
>>>While my bosses love the app, they aren't going to allow it's full usage until the memory gets trimmed down. This being the first VFP app for this company (and me...), it would mean back to maintaining there old broken-down obfuscated system. I'd like to be able to UPGRADE them...
>>>

Once you get beyond the allocation, you then have to attempt to use as little as possible, or rather use what you have efficiently.

Try to segmentalize the app as much as possible. Remember, you can use multiple procdure .PRG's and you can open/close them one at a time (SET PROC TO myproc ADDI ; RELE PROC) Same thing with SET CLASSLIB and RELEASE CLASSLIB.

Categorize your procedure files and class libraries and open only those that you need. Object-resident methods are nice, but sometimes they tend to be huge memory hogs. Make full utilization of CREATEOBJECT() and ADDOBJECT/REMOVEOBJECT.

After doing some of this, you may find you'll be able to further reduce the size of your app's memory footprint. (make sure to leave enough room for the app to function with larger tables)

HTH