>>I'm the Network Administrator at a small insurance company. This Monday our Visual FoxPro programmer put his new database on the server.
>>Since then our users get either an not enough memory to run Visual FoxPro error or are kicked out of windows to Dos.
>>
>>We have Pentium 100, with 16 meg of RAM. Windows for Workgroups and Novell Netware 3.11 server.
>>Visual FoxPro 3.0, WordPerfect 6.1, FacSys.
>>
>>Already searched Microsoft knowledge base. No answers.
>>Tried to talk to someone at Microsoft, they said $95 a question.
>>
>>Consultant told me the windows resources are being used up and there's nothing I can do about this.
>>I'm at a loss. I can't believe that this can be true.
>>
>>There must be something I'm overlooking.
>>If you can make suggestions, I'd really appreciate that.
>>Or tell me where I should be looking for answers.
>>
>>Thanks! jwlov@localnet.com
>
>is the 'lockout' immediate or does it happen after working w/ the system for awhile? because you're running under wfw, you need win32s on each machine (installation of this system on each machine should do this if your programmer did his job).
>
>system resources are generally 'lost' under print routines. a little more info in what you're doing before you get thrown out would help...

Dave - Thanks for your e-mail message, I'm very new at internet and wouldn't have quickly known how to get the replies. THANKS!!

the win32 is installed on each machine. Our users are used to loading many programs. Typically WordPerfect 6.1, FACSys, TinyTerm (Corban a UNIX system), and misc things like clock, and rolodex.
They have been able to do this fine, and then add FoxPro for DOS, no problem. Now with all this, adding VFoxPro immediately brings up out of memory error. So I told many to not load as much until I can figure this out.
Other users are used to loading two copies of DOS FoxPro so that could quickly toggle between windows. With nothing else open, they can't open two copies of VFoxPro. By noon, system resources are down to 13% - 8%.

Yesterday, FoxPro programmer suggested that we get Developer's edition. Right now everyone is running standard. When I called Microsoft to purchase it, the salesman told me that that won't help our problem at all, but would't
give me any further direction.....