>This happens intermittently. They'll both work when you first get into the system (VFP or my compiled app) but after some amount of time will stop working. Getfile() will simply do nothing at all and Getprinter() will flash an empty messagebox and then flash "Printer is not ready" (or something like that).
>
>This has been happening on my machine (and only my machine) for the last year. I've just considered it a minor annoyance because it never happened on anybody elses machine. But now it happened on the machine where I'm installing my app. Which, BTW, is a fresh install of the OS.
>
>I'm in VFP5 with Win95 OSR2.
>

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