>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.

Definitely suspicious. Get the connection problem resolved. When you say you downed the Novell servers, was that permanent? Maybe you're having too many connections? Not sure since I haven't run NT Server for many years. What service pack for NT? Are you sure you're cabling is good?

Another issue, which I don't know if it's relevant to NT...isn't there a quick connect to mapped drives? Meaning when a workstation logs in the mapped drives are created but not tested til the user actually hits them.

>
>Secondly, we have added McAfee's Suite to the NT Server itself to scan all files opened during work session.

This could also be the problem. Seems like it could be causing timeout issues. I used to be a big fan of McAfee, but have actually switched to Norton. I found McAfee to be unsatisfactory for my needs. But, in any case, it should be possible to test in a limited way (with users proven to conduct safe computing).

>
>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.

Well, I think you just have, actually. The issue is to isolate the component and it maybe more than one. For example (and it might be a lousy example) the time McAfee is taking to scan files is causing a timeout on a bad cable on the network.

> 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).

What about printer? I gather since you didn't answer that question, you haven't added, say an HP (there are some rather infamous HP printer driver errors, from what I've read in the newsgroups).

Good luck. Nasty problem to diagnose! Keep us posted on what you find.