You got it. (As soon as I figure something out <g>.)

>I'd like to hear your results.
>
>>Well, Tore, this is a better explanation than anything I'd been able to come up with. I'll do some more experimenting. Thanks.
>>
>>>I may be wrong, but I think I read somewhere that some commands, COPY TO may be one of them, does not respect the path of a file, if a file with the same name is 'baked' into the exe, the 'baked in' file will be used instead.
>>>
>>>>Interesting shot :-). Yes. But... The executable is running on a file server with a path name to a mapped drive letter "R" that looks back at the development machine where the source file actually exists--on the C drive, i.e., C is mapped as R on the machine where the executable runs (this is a home grown backup app). So the file stored in the project shouldn't have the same full path name. Am I overlooking something?
>>>>
>>>>>Just a shoy in the dark. Do you also have a file called ADD.BMP added to your project?
>>>>>
>>>>>>Anybody seen this?
>>>>>>
>>>>>>

>>>>>>LOCAL ;
>>>>>>   lcFile,;
>>>>>>   laSrc[1]
>>>>>>
>>>>>>lcFile = "C:\PROJECTS\COMMON\ADD.BMP"
>>>>>>
>>>>>>IF ADIR(laSrc,lcFile) > 0
>>>>>>   COPY FILE (lcFile) TO <destination>
>>>>>>ENDIF
>>>>>>

>>>>>>
>>>>>>And the COPY FILE line throws an error 1, "File does not exist"--ONLY in compiled executable (.exe with Fox runtime only) but runs just fine from source code? (I started out using IF FILE(lcFile) but changed that thinking it might be the source of the problem. Changing to ADIR() made no difference.) BTW, the file DOES exist.