>>>>>>>>Copy out to a temp file, modify andrun
>>>>>>>
>>>>>>>I had some difficulty trying to do this.......
>>>>>>>
>>>>>>>Do you have any sample code that extracts the FRX and FRT from the EXE program ( copies the FRT and FRX to the temp folder) ?
>>>>>>>
>>>>>>>thanks!
>>>>>>
>>>>>>In addition to Tores message.
>>>>>>
>>>>>>Check SYS(2450) search order, also use a generic name for the copy as SYS(2015)
>>>>>>
>>>>>>like
>>>>>>

>>>>>>lcTarget = ["]+ADDBS(GETENV("TEMP"))+SYS(2015)+'.frx"' && wrapping " for space in path
>>>>>>COPY TO &lcTarget
>>>>>>

>>>>>
>>>>>You mean
>>>>>

COPY TO (lcTarget)

>>>>
>>>>I will never learn what works with () and what needs &. So for the rare cases I need it (aside from SQL where Im sure about it) I use &.
>>>
>>>The problem is that & will fail if there are any spaces in the path. The rule is quite simple. Use () when VFP is expecting a name and only a name. In this case, it expects a file name, so () works.
>>>
>>>Tamar
>>
>>Hi Tamar,
>>
>>nice to see you.
>>
>>I try to remember it.
>>BTW my code will not fail with spaces. There is the quotation mark kludge. :)
>
>FWIW, when I inherit code, seeing '&var' in the code is one of the signs to me that the code is fragile and should only be changed with great care.
>
>Tamar

Ooops
If it comes to special things sooner or later there will be an (intended) &lcVar. It's so straight forward. But you are right, one has to deal it with care. Just like a GOTO comand. Could create havoc; BASIC w/o FUNCTION (*.*); but used the right way a nice tool.