>Way back in FPW 2.6 there was a fix for this, but the problem supposedly went away with VFP. Does anybody have a definitive explanation of why this happens and how to fix it?

If you developed on drives other than C:\ the FPW exe was looking for that path. The fix was to patch the exe - I wrote one of those for a special distribution, after reading what the others did<g>. AFAIK this is fixed in vfp never had any problems with projects on drivers > C:.

>I develop and compile on my D: drive. The problem cropped up again the other day when a client with a cd rom designated as D: has to put a disk (any disk) into drive D: in order to be able to run the application. My colleague, who also has a cd rom designated as drive D: has no such issues when there is no disk in the drive.

If it is REALLY as you describe (same exe, same installation) and you also have checked the fringe cases (different .fpw, foxuser.* and other environmental settings of vfp and no codepath in your app different on existance of flag files <g>) this points the finger to the machines themselves. Either something in the registry or a different setting on the machine path or the installation of ocx - perhaps something is found on your coworkers machine in a "common" directory which triggers the error message on the other machine. To get to the bottom I'ld probably first try an xCopy-install of bare-bones vfp (just the exe and the dlls), start vfp and run the program from debugger until the error crops up.

HTH

thomas