Hi Guys - Thanks for the responses.

It's Win95/98 clients running on an NT network. John - Thanks for the Netbeui suggestion. I'll try that. Also, after playing around with config.fp and moving all tmp files to a local directory, things have sped up tremendously. I also set files=99 and buffers=20 in the config.sys of the worst offending machines (p100's with 16MB RAM, Win95). The problem seems to have disappeared, but it's so sporadic, I can't say for sure.

If it returns, I will certainly investigate the Netbeui idea. You both asked about network type - is there anything particular to NT that I should be aware of that could be causing such a problem?

Thanks again for your help!

>>I just "upgraded" a client's system from single user to network (fox2.6). This in itself is no big deal - I probably have 100 clients on the networked version. These guys are experiencing wierdness though which I haven't seen before. Very sporadically, their systems "freeze" while loading my exe (stand alone extended). The freeze seems to be happening while loading Fox, as it usually happens before my routines start to execute (though sometimes it freezes during my splash screen).
>
>If you aren't loading the exe from the client, copy it there and run from the workstation. This will cut network traffic significantly. Also, you need to remove netbeui if you are running multiple protocols. It is a VERY chatty protocol and if you have more than about 20 pcs, it can be problematic.
>
>What kind of network? NT, Novell, etc.