Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Syntax error tracing
Message
De
01/12/2016 19:36:08
 
 
À
01/12/2016 17:46:26
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Divers
Thread ID:
01644145
Message ID:
01644228
Vues:
34
>>The .ERR file is simply reporting the source for a line of code it can't compile. If VFP is trying to compile that line, AFAIK "ADD OBJECT" is not a valid VFP command.
>>
>>If that's the case, where did it come from? Do you recall how you added that line to your class?
>
>If I'm not mistaken, ADD OBJECT is a clause that could appear in DEFINE OBJECT / ENDDEFINE block -- which means it really only should appear if defining classes programmatically rather than visually in a VCX. This would lead me to think at some time Class Browser was used to view the source code, then some of it was copy/pasted into the snippet window within the VCX class.
>
>Of course once you've mucked about with a VCX enough, you're likely to damage the VCX further rather than repair it (especially if you open the VCX as a DBF and muck with the contents of memo fields directly -- don't ask how I know this). It's usually easier to restore a good copy from a backup at that point.

Hi Naoto,

Thanks for your insight however I can assure you in this case the .err file was constructed before I opened or browsed the .vcx file.
And yes you are correct it was easier to restore a good copy from my backup. Whished VFP would have had an automatic backup for .vcx files as there is for .prg files.
Regards,
Koen
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform