Vlad,

Very interesting. This matches my experience exactly, except it is all with 2.6/Win. My history:

1. Used to have everything on C:, never a problem.
2. Moved to a different machine and added a 3 GB second drive, formatted as 1.5GB each to D: and E:.
3. Put FPW and FPD on D: and all source and apps on E:.
4. Some clients started noticing the problem. It always involved removable media drives on their computers (ZIP or CD). If they inserted a disk first, no problem.
5. I guessed the problem was having the stuff on different drives so moved everything to D:. Also tried a different machine. This shifted the problems for some clients but did not resolve. Note that I did not revert to C: in these attempts.
6. The initial failures involved BMPs. If I removed them from my form, no problem. These were built into an APP, but of course the generated SPR was including the original path, which never was a problem before.
7. I modfied my base BMP classes in my GENSCRNX libraries using the *:PICTURE directive so that no pathing was indicated in the GETs for these objects. This had no impact on the problem!
8. I could only resolve this by sending physical copies of the BMPs with my app and changing the picture to refer explicitly to .\system\filename.BMP. This seemed to get me out of it for a while, but...
9. On another APP, I hit the same error on a USE staement for a temporary file I was processing. There was simply no way pathing was involved in this (or at least none under my control).
10. This entire time, another developer could produce builds that ran on the same client machines with no problem. She, of course, was on her drive C:.

I am going to move all FPW/FPD stuff back to C:.

Have you noted this in VFP5 or only VFP3?

Randy

>There's a known bug (already discussed here on UT) related to where the files are located when you build your APP/EXE. I first noticed this problem for BMPs, but many other reported the same thing for other file types. This problem is not related to a hardcoded path. Probably it's a bug in the build process.
>
>The best solution I found is to build APP/EXE from C drive (ALL files on C drive) and hope that the client will have a C drive.
>
>Although, I never had this in FPW 2.6, but only in VFP.
>
>Vlad