>>>>>After compiling an APP in Foxpro 2.6a on a machine that has both a C: Drive and a CD-ROM, When try to pull up the executable I get Error Reading Drive D:, d being the CD-ROM Drive. If I put a cd in the cd-rom drive it solves the problem but that is not an acceptable fix. I tried to find somthing on Microsofts Knowledge Base but was unsuccessful. If any one else has this problem please let me know the outcome. Thanks
>>>>
>>>>
>>>>Did you compile this on your C drive or D drive?
>>>>
>>>>I think all fox apps should be compiled on C drive becase of problems.
>>>
>>>This is a known problem with 2.6. I think they fixed it with Visual FoxPro.
>>>
>>>Dana
>>
>>Dana,
>> They may have.. But that is NOT an acceptable answer for still running 2.6 apps, to be re compiled under VFP 3/5 and solve one problem, while adding a few dozen more..
>>
>>Sorry, the best idea is to remove the bogus drive info from the application and drive on with it...
>>
>>Thanx!
>>
>>Tony Miller
>>Vancouver, Wa
>
>Tony,
>
>I never suggested that the fix was to move to VFP! However, that said, removing drive D: is not always a possibility. Here, we use a server on the NT network that is physically drive D:. When compiled on that server, the problem rears its ugly head. We have found no solution, except to MAP the drive to a logical K: (which is above any add-on drives our users may have) and build the app with K: as the Default in FoxPro. Even MicroSoft admitted this problem. The home of the project has to be K: (when told that the project has moved, answer yes to making this the new home).
>
>Remember, I didn't make the bug...and MS didn't seem to mind leaving us without a patch for it, even though there must be a lot of businesses still using 2.6!
>
>Dana

I am sorry, I took your answer to be similar to MS's answer on fixing the memory error with FP 2.xW and faster machines..

Thanx!

Tony Miller
Vancouver, Wa