Some ideas that come to mind:

- The disconnecting from the network could definately cause the problem.
- Delete the FOXUSER.* files.
- I've seen times, especially in Win9x, when VFP terminates abnormally, it leaves temp files on the drive. The solution was to place all VFP temp files in their own folder then DELTREE the folder in the autoexec.bat, then recreate it.
- SCANDISK the suspect drives

>Nancy,
>
>Thank you for the reply! In response to your questions, the only thing that we have done drastically was down a Novell Network server off the existing NT server we have always had running. Since then we have had network connections problems with Network Neighborhood; however, that is a different problem in itself. If if will lead credence to the problem, the trouble that we are experiencing is frequent problems connecting to our NT server. Windows keeps prompting various users at various time if they wish to reconnect next time they log in. However, if you go into My Computer and click on the map drive (marked with an x), the drive opens because it is already connected.
>
>Secondly, we have added McAfee's Suite to the NT Server itself to scan all files opened during work session.
>
>I have eliminated the fact that VFP6 is causing any problems. We had these problems before 6, but I am not going to rule it out. I can find it to be an index problem because we reindex every night. I guess it could be a corrupt index, but I am sure that we would not be able to open that file or everyone not be able to open a particular file. It is not a video card compatiablity issue and it is not an OS issue. We are running all systems (NT, 2000, Me, 98, and 95).
>
>Any clues?? Thanks!!