>>If you compiled the app or exe on a drive other than C: it won't work.
>>
>>Put a disk (data, not music) in the D: drive. It will probably work
>>
>>Then, move your project back to drive C:, recompile. No problem.
>>
>>Adolph Santorine
>>
>>adolph@schedulestar.com
>>http://www.schedulestar.com
>
>
>Folks,
> A while back someone released a tool to fix this in 2.6 apps. I saw this up on Compuserve , in the the forums. What it did was, go looking thru your application for any reference to any drive other than C:.
>
>I don't remember who the author was, but someone whohas access to compuserve may want to look in the libraries (hint hint..)
>
>Thanx!
>
>Tony Miller
>Vancouver, Wa

I know about this tool. In fact you can do the same with any hex editor that has a Find&Replace feature. And this really fixes some problems.

The real problem is that you can still have that error when there's no reference to any other drive than C: in any file. This is a bug in FoxPro and the only workaround I know is to build everything from C:

I "tested" this bug for 2 days a few months ago and my conclusion is that during the build process, some references to other drives are hard-compiled into the APP/EXE. Of course, these references can be found in the APP/EXE file, but is almost impossible to be sure you found them all and that you change only these references. (If the reference is hard-coded as "D:" you can be almost (how do you know if it's the drive or just a coincidence?) sure it's about the D: drive. But you can't Find&Replace all "D"s and "d"s with "c".) I couldn't find a 100% sure method to fix the bug by doing a replace.

In the same time, building the project from C: eliminates this problem and it's much easier and safer to do it like that than to try to fix the compiled file. This is why I wouldn't recommend anyother tool for it.

Vlad