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

David,

I'm having very similar if not the same problem.

Could you provide a reference to the article. I just got the May FPA and looked through it as well as April's and didn't see this article.

Thanks,