>>I agree that this has to do with the number of files that are open. I've seen this kind of thing happen in older FoxPro versions when you run out of file handles. FoxPro can't open a file, but doesn't bother to report an error. Opening a DBF without its corresponding CDX is a classic example of this.
>>
>>It sounds to me like either the workstation or the server is running out of file handles. One expiriment you could try would be to try opening several files on a workstation that is having this problem (Word documents for instance). Also, try opening several files on the server from another workstation. See if you can generate an error. This may not work on the server because more file handles could be available when you run the test, but it's worth a try.
>>
>
>I'd have to disagree....I'll almost lay odds that updates aren't happening at peak traffic times, variables getting lost...things like that are happening also. I'm betting that there's either a hub or a router about to go bad.

Dorris, you'd win your bet. File handles are NOT the problem, but peak traffic IS. And we've had exactly what you say - variables lost, entire routines not running (see my other message on SEEK()).

Thanks to all of you who wrote in - I now have ammunition for the network guru who arrives Saturday from the East Coast, bringing about 100 lbs of hubs, routers, cables, etc.

Thanks to Vlad, Cetin, Michael, Dorris, Josh, Bob & John. And also to Dave & Mark for a chuckle :-)

Barbara