Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
HACKING the FRX in an EXE
Message
De
03/12/2015 08:25:42
 
 
À
03/12/2015 08:18:51
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de rapports & Rapports
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows 7
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01628280
Message ID:
01628368
Vues:
52
>>>>>>>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
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform