Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Invalid Database Number
Message
From
14/05/2001 13:37:52
David Fluker
NGIT - Centers For Disease Control
Decatur, Georgia, United States
 
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00506865
Message ID:
00506935
Views:
21
>Why would a FPD2.6 session be limmited to only 25 tables opening? Of course I have an application that needs 26. Now 2 users are getting Invalid Database Number errors opening this one form. I login into the same app and it happens to me too, and I have full rights.
>
>From my workstation there seems to be no difference between FoxPro & FoxProX opening the same form set.
>
>Any ideas on this one?
>
>__Stephen

Usually this has to do with the amount of memory the FoxPro sees available. Not enough memory and it defaults to standard FoxPro with 25 workareas. If the computer has enough RAM, then it's probably a configuration problem or a conflict between the OS memory manager and FoxPro's.
-If you're running DOS, check the CONFIG.SYS to be sure the memory manager is set up properly. Look for the EMM settings.
-If you're running Windows 9x, check the properties setting of the application's shortcut to be sure enough memory is being allocated.
-Windows NT can be tricky. It automatically sets memory based on how much memory the app requests at startup, while FPD sits back and waits to see how much memory the OS is making available. NT decides your FPD app doesn't need much and gives it a small amount, so Fox defaults to regular FoxPro. We have found these settings to work. Set DPMI memory to 4MB or more. Set conventional memory to 630. Don't set it to Auto or 640 because then the NT memory manager kicks in.
-Windows 2000 seems to do okay with Auto settings.

Good hunting!
David.
Previous
Reply
Map
View

Click here to load this message in the networking platform