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

We had a very similar problem. I develop everything on my C drive but somehow
a reference to D: got stuck in the EXE and when we ran it on a test machine with
a C: and a D: (CD-ROM) with no CD inserted, "Cannot read from drive D". Put a
CD in, no problem. What I did was open my EXE in a Hex editor and looked for
D: and toward the bottom there was a reference to a D:. So I just changed it
to C: and no problems. That's kinda dangerous, but I there was no need for my
EXE to point to any D:. It didn't cause any problems and it's been in
production for well over a year and a half. But if your users are getting this
message for a C:, then it sounds like their machine is screwy. It's as though
their machine thinks their CD-ROM is on drive C:. But at the same time, I
wouldn't think that more than one person would have a screwy machine like that.
I can just tell your problem is based on this one broad error of foxpro not
liking it if it tries to read from a CD-ROM drive if there's no disk in it,
nevermind if there IS one there and what it's LOOKING for ISN'T there! That's
what's so stupid, it doesn't mind if what it's looking for isn't there as long
as there's SOMETHING there! But you could just look for other drive references
in your EXE through a HEx editor. Because even when I found the D: reference
in the Hex Editor, I never could find one in *ANY* of my programs or projects
or anything. It just got stuck in the environment somehow.

Steve.