>>>>>Yes FILE() will always find a file embedded in EXE as long as it run from inside EXE. If it's executed from external FXP/APP, it'll not see files inside EXE.
>>>>>
>>>>
>>>>Thank you, Sergey.
>>>
>>>Keep in mind that it'll also find a file with the same name outside of EXE on VFP search path if internal file is not present. IOW, it's impossible to tell if file is embedded or not.
>>
>>Yes, I understand. For me it is important that the .EXE program will find the file, no matter where. That is, I will probably place a copy of the file on the drive and include it in the .EXE. I want to be sure that the program will branch to the special procedure for this customer.
>
>Just some FYI's that come to mind during my previous testing with this.
>
>1. Assuming there is an embedded file in the EXE and an external one, you can force it to use the external one by fully qualifying the path to the file.
>
>2. The internal file can not be written to, so there is an inherent way to tell which one is selected via try... catch...
>
>3. You may be able to tell which one is selected by obtaining the full path to the file select using the DBF() function and if the folder does NOT exist (since it will specify the folder where is resides on the development maching, you can then tell that it is using the internal one.
>
>Hope this helps.

John,

Thank you for your input.