Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
BUG: return a new object by reference fire a C5 crash
Message
 
 
À
14/04/2004 14:22:37
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00893984
Message ID:
00894895
Vues:
18
Fabio,

In the tens of thousands of lines that I've written in VFP since VFP3 shipped I have never once needed to use m.this or m.thisform. If you don't have control over your development environment to forbid the use of a table/cursor name of this, thisform or thisformset then that's more a problem with your environment than it is with the VFP language itself.

You are free to continue using m.this. You are also free to continue to experience the random C05 errors that m.this causes. Your position on the matter is a rather silly high horse to sit on, considering that a C05 is quite likely to cause table and index corruption in addition to your end users losing the work they are trying to get done.

>But write This without m. , not optimal programming is one.
>
>David, is useless that you insist, who you do not use m. you mistake.
>
>When, on VFPXX VFPT set This,Thisform,... special internal reference,
>and not search for a "This" table or field, i remove m.
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform