>Does anyone know of any memory problems, such as memory leaks, that Visual FoxPro 3.0 may have? I'm currently running VFP 3.0 under Windows 95 on a Novell network and am unable to run VFP for more than about an hour of development time without running out of memory. This causes problems ranging from not being able to open more than approximately 5 tables of a database at a time ("Too many files open" error message results) to having the numbers "5" and "6" appear in the vertical scrollbars of all the windows (in place of the up arrow and down arrow, respectively), to having numerous, annoying "Illegal Protection Errors" causing VFP to crash altogether. This is EXTREMELY frustrating. Does anyone know if this problem was fixed under VFP 3.0b? Currently, VFP 5.0 is not an option because the resulting .EXE needs to run unders Win3.1. I know that it is eating up memory/Windows resources because I used the Win95 Resource Meter and visible watch the resources being depleted. If anyone
>can help, it will be greatly appreciated.


I would highly reccommend 3.0b (if your stuck). For the 20 or $25 it is worth every penny.

Tom