>
>Are you running in a network environment, from a network drive? The only time I've seen this behavior from GETFILE() (I don't use GETPRINTER() in my own code, so I don't have any first-hand experience with it as a problem) is when the network connection for the current working directory broke (server reset, network timeout or other correctable event) and was reconnected by Windows in the background; at times, open file handles in the CWD for temporary files were lost, or GETFILE() couldn't resolve the UNC or drive mapping for the CWD, the base point for GETFILE().

I am running in a network environment. That may be the problem. One thing I left out is that if I close VFP (or my app) and get back in then it starts working ok again.

So assuming that a network disconnect and reconnect is the issue, what's the fix? Is there a Netware Client setting I should change?

paul