>I'm running into a really confusing problem that is just destroying the credibility of VFP here. We have a VFP exe that seems to have problems when the EXE is located on our workgroup server and is executed on a client PC. In our workgroup, everybody has the VFP runtime installed on their PC (yes, SP3), and they have a shortcut on their desktop pointing to a compiled VFP exe (about 500K in size) that is sitting on our server. We like this approach because upgrading the app requires only that we upgrade the EXE on one machine. However, we frequently run into this problem: The application bombs with error messages that suggest that the EXE itself is becoming corrupt as it is being accessed/loaded over the network. For example, we get sporadic error messages that a procedure that is included in the EXE is not found. If the procedure is named MYPROC (and was of course included in the VFP project as MYPROC.PRG), we will get an error message saying something like:
>
>"C:\Windows\Temp\MYPROC.FXP is not an object".
>
>The app is relatively simple in terms of the demands it puts on the network. It only accesses one table (also stored on our workgroup server, with a memo file and 3 index tags). Plus, the table is very small, only 200 or so records. The app runs fine a lot of the time. The error is sporadic and unpredictable. The app runs perfectly when run on the workgroup server itself or whenever I run it on my notebook computer or my standalone desktop computer at home. If you have seen any problems like this, PLEASE RESPOND!! In particular, if this is a network problem you have seen before, I need to know what to tell our network gestapo here so the problem can be fixed. Thanks very much!!!

If you need a quick answer, be sure to search for existing threads on this topic - there have been a number of broad and deep ones in the last few months.

If that doesn't help, the "network gurus" are going to want to know every excruciating detail about your environment:

- Server hardware and NOS, including service packs/patches
- Client hardware and OS
- Networking infrastructure
- Client network interface software e.g. device drivers, protocol(s) being run, network client(s) installed.

If you're running on Novell, the consensus seems to be to update all clients to the very latest version of Novell Client32 (currently 3.1x ?) (if you're using the Novell client). Aggressive default settings in earlier versions sometimes caused intermittent problems of various kinds.