>Jim,
>
>This isn't really the issue. I use all of these techniques for dealing with drives letters and paths at run time.
>
>There is some strange behavior that causes this message even though you have no drive hard-coded anywhere in your source.
>
>I have some users get the message on a GET clause that references BMP files that are built into the project. There are a few other combinations, too, but never is there a drive in the code.
>
>In cases I have seen, it happens to people that have a CD ROM drive that has no CD in it. If they run with a CD inserted, no problem. I have debugged, checked setting for SET( 'PATH'), and several other items when this happened to no avail.
>
>Of course, I've never seen it personally on any machine, which makes the fix even harder to work on.<s> Another interesting factor is that this started when I switched development machines. Another one of our developers can build the same APPs on her machine from the same source code, GSX drivers, etc., and users don't get the error.

For this problem, if any drive other than c: is the offending drive, the advice given by Mr. Hairston (FoxPro Advisor, June 1997, page 60) makes sense - he gives solid advice on how to find non-c: references in the application and how to eliminate them, But for my problem, this does not help, since it is drive c: that cannot be found.