>>>>>>
>>>>>>Today I saw another error in the error log. The error says:
>>>>>>

>>>>>>Cannot read file c:\users\dmitry\appdata\local\temp\password.fxp
>>>>>>

>>>>>>
>>>>>>Note that the error points to the location on my PC (my development PC). The end user does not have the c:\users\dmitry....
>>>>>>
>>>>>>How could it be that at run time his application attempts to read a prg/fxp file from location on my PC (that is, in location that does not exist in his environment)?
>>>>>>
>>>>>
>>>>>Regarding the above problem where the application is looking for the FXP in a folder that only exists on my PC.
>>>>>Note that the end-user gets this error. And I can't think how the application would know MY local drive name.
>>>>>Question:
>>>>>Does VFP 9 - when you compile and build the EXE - stores MY local folder name anywhere in the EXE?
>>>>>
>>>>>TIA
>>>>
>>>>If I'm not mistaken the full path to the original PRG is contained within the FXP file (the structure of which is probably similar to that of an .OBJ file -- some sort of "header", followed by different "code" and "data" sections, with some of the "data" sections containing information of the original source files). An APP is (from what I gather is simply a "library" of FXP files -- which has its own "header" and "contents" section). An EXE (and by extension a DLL) file is simply like an APP file but with an EXE "wrapper".
>>>>I do remember back in the FoxPro DOS and FoxPro Windows days one annoyance that occurred was if your source directories weren't on your C: drive. In particular this could be situation where you partitioned your harddisk to have C: dedicated system and applications, while having separate parittion to keep your data. Often this meant your data partition ended up as D: drive. Where this became problematic was when a customer didn't have this configuration and the D: drive was the optical drive (i.e. CD-ROM or DVD-ROM), and they'd have to insert a disc in it for your program to operate properly. Unfortunately it wasn't entirely clear when this internal directory information was being used -- sometimes the problem would occur, and sometimes not. I do remember after moving from FoxPro DOS/Windows to Visual FoxPro the problem largely didn't happen (save for the times when errors would occur and the original source folders would be displayed).
>>>
>>>Thank you for your input. I wish there was a way to recompile the PRG file into an FXP such that none of the local path is saved. And only the content of the PRG is compiled.
>>>I think - I am guessing - that FOXUSER.DBF has something to do with the what is saved in the FXP file.
>>>I wonder if I delete the FOXUSER.??? before building the application, none of the file PATH is saved in the EXE.
>>>If someone knows, please let me know.
>>
>>The *local dev temp* folder reported in the error message is what VFP is using to compile the fxps for the prgs included in the project at build time. The path to the compiled fxp is recorded in the exe (if the app/exe is built without encryption, you could see the path to the fxp recorded in clear in the app/exe).
>>At run-time, the exe acts as it's own file system (I don't know exactly how the file lookup is done, but I think fxps and other compiled modules are looked-up first in the exe. If they're not found there, then the next step is the search on the path recorded in the exe; failure at this step is what probably generates the error.)
>>*
>>Obviously, you'd expect that all modules included in the project to be available in the exe (and they probably are), but the exe may not be properly available when the error occurs.
>>Long story short, as others have suggested before, there may be network errors, or other interference (like anti-virus scanning) preventing the app/exe to be loaded properly.
>
>Thank you for your input.
>You wrote:
>>>(if the app/exe is built without encryption, you could see the path to the fxp recorded in clear in the app/exe).
>How do you see this in an .EXE file? That is, what tool do you use to view the inside of the .EXE file?

Just open it with a regular text editor.
*