>I have a FoxPro 2.5 program running on a Novel 4 server. There is PLENTY of space available on the volume where the application is stored. All of the users have their Novel space limitations set to UNLIMITED. However, occassionally (although it is becoming more frequent) the users try to add a record to the database and they get an INSUFFICIENT MEMORY ON
message which then locks up their workstation and does not allow them to add the record. The table has only 10,000 records so I know they have not reached the foxpro table limits.
>
>The user does NOT want to upgrade anything at this time. What can be causing this????
>
>GINGER.PIERCE@MSFC.NASA.GOV
Ginger,
I don't recall a memory error identifying a volume name, so this may not be right, but I beleive Insufficient Memory is a problem is involving the workstation, not the server. If this is FP for Windows, check the MEMLIMIT line in your config.fpw. If memory serves, it should look something like "MEMLIMIT 60, 4096, 12228" where the first number is the percentage memory used, the second is the minimum and the last is the maximoum used. If this is FP for DOS be sure you properties are allowing enough memory to use FoxProX and not just standard FoxPro.
On the other hand, I've had several "Not Enough Disk Space" errors on a Novell server with plenty of volume space. It turns out that if the user who created the database file is no longer a user on the server, that file is limited to the guest disk space limit. For example, I look at a directory and see 500 MB available, yet when I try to add a record to a table that is 98K in size I get "Out of Disk Space" because the developer who created the table is no longer on our staff and the file now has an unknown owner and is limited to 100K of disk space. The quick solution is to copy the file to my local drive, delete it from the server, then copy it back. Now I am the owner and it works fine. The permanent solution is to have it owned by the administrator. The error might be caused by the .dbf, the .cdx or the .fpt growing too large.
Good luck tracking this one down.
David.
