Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Do FunctionName.prg
Message
De
19/05/2021 18:36:07
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., Nouvelle Zélande
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
01680170
Message ID:
01680613
Vues:
41
>>In the project all PRG files are in the folder \AppFolder\Programs Basically my project structures is as follows:

OK. VFP can cache fxp in the PROGWORK location though not usually inside an exe- but still worth checking for PROGWORK= or TMPFILES= in the project's or client's config.fpw.

For completeness, though I'm sure you would have said: not using Defox or other protection scheme?

How about Execscript() or Evaluate() or _execute() or _evaluate() or Compile or other use of interpreter that might involve a temporary fxp that goes out of scope?

I have seen password managers that build strings to be macro substituted or execscript()ed that was considered more secure than plain VFP code, not one of those?

Just in case I'd use gofish to do a search for dmitry in the project. Also for compile, execscript(), evaluate(), _exec, _eval ... Might be an "aha" moment to save you hours of fun...
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us.
"
-- Shakespeare: Coriolanus, Act 1, scene 1
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform