>>>I wrote a EXE in vfp50 - The program is on my PC. When the data path
>>>is set to my local harddrive, it works fine. When I set the data path
>>>to a network drive it locks up. This is my second program that is set
>>>up like this and the first one worked great. You would think that there would be something wrong with the database on the network, but I check it and I performed a VALI DATA and it is OK. what do I do?
>>
>>
>>Sounds to me like one of two things:
>>
>>1) It is still looking for data on the local drive due to the way VFP saves the paths in the DBC.
>>
>>2) The CONFIG.FPW is pointing temporary files to non-existant directories.
>>
>>Craig
>
>hi Craig and thanks for answering... It is not the CONFIG.FPW and the program
>finds the data on the local drive.
>This is the test I did.
>Station 1 - my computer
>Station 2 - the computer that locks up
>
> On station 1, I open the database that is on the network drive exclusively.
>I ran the program from station 2 and I am getting a sharing violation.
>That is what I am suppose to get. On station 1, I closed the database on the
>network drive and on station 2, I ran the program again. It locked up..
>This is my second EXE and I did not have this problem on the first one.
>any more ideas?

Lets look at this more closely..

- What type of network? NT? Netware?
- Did you create setup disks and install the application on PC 2?
- Have you run a scan disk on PC 2?
- Are temp files going to the local drive or the network?
- What exactly are you doing in the program when it locks up?
- What is the client OS? WIN NT, 95?
- When the program locks up, can you shut it down or do you need to reboot? Can you launch other programs?

Craig