Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP exe modification
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Versions des environnements
Visual FoxPro:
VFP 9
OS:
Windows XP
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01420991
Message ID:
01478221
Vues:
55
Damn near a full year later I just ran into a off situation with an execscript that could not find a VCX. I was wondering if it was related to the same issue I had last time. I remembered this thread and thought it might help. In this case the createFactory() call worked perfectly and I'm all set.

So thanks again.

Alan
>>OK I have a strange situation.
>>
>>I have a bug in a just released version of our POS app. Its not a show stopper but its highly annoying. I'm trying to find a way to get an update out with out a new release.
>>
>
>I hate when that happens.
>
>VCX's can't be called like that (as you've found out). Forms are also an issue. Functions seem to work fine. I don't think I've tried replacing an entire VCX but I tend to embed a DoForm() function in which can call a form (and have it still be able to see the other libraries). I also tend to embed a CreateFactory() method which creates an instance of a class for me (and gives a central place to set various properties). Both could be used to call out to an external PRG/Class/Form.
>
>If you have a hook point, you could try attaching a simple object to the _screen object that has the new code for the method you want to override. Then, use BINDEVENT to capture the method that has the bug in it and redirect it to your _screen object. You can get a form reference via AEVENTS, if necessary.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform