I have an application for which the .FSL file runs about 240 Kbytes, and the listing fills more
than sixty pages. It's a tracking database for custom ic's used in our medical products.
The main form includes about ten buttons, each served by its wad of code.
This is running in a Gateway Pentium with 16 Mbytes of ram.
Any attempt to bring up the de* generates the out of memory error, and shows the spot in
the listing where it ran dry.
Same thing happens in a system with 20 Mbytes of ram.
I had seen this in version 4.5, from which I have just upgraded.
Wondering if this is due to a (modifiable) default parameter, or is it the end of the road ??
Any clue would be great !