>Hello there,
>
>>There's an article in this month's FoxPro Advisor, written by Jack Hairston, about what to do when a FoxPro executable yields a "Cannot read from drive x:" message, when x: is a drive that exists on the development machine, but cannot be guaranteed to exist on the user machine. It essentially explains how to strip all non-c: references from the project file.
>>
>>Well, my problem is a little different. Some of my users are getting that message, but it is in reference to drive c: - a drive that one would assume always exists, and I certainly cannot strip from my machine.
>>
>>Has anyone run into that variant, and what whould you suggest to cure it?
>>
>>Thanks in advance.
>
>Assuming a drive will always be there is not a really good practice. There are times when you may be running the application from a drive d: or other drive. I don't know what's going on with your application, but a good way around it is to set a PUBLIC variable at the begining gDrive or whatever and use that throughout your application instead of hard coding a drive letter. This way, you can store the value in a .mem file or a table and update it in one place.
>
>Hope this helps.

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.

Regards,

Randy