Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BUG: skip the Assign destroy object or fire a C5 crash
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00893546
Message ID:
00894553
Views:
24
>Then why is there no THIS_Assign?
>
>Simple:
>
>because this, thisform, thisformset they are readonly
>
>But you can define THIS_Assign,
>a useless procedure because Error 1930 Catch the assign before VFP call the
>THIS_Assign.

Then why are you complaining? Object's don't have an assign event, so don't do it.

The C5, BTW, is caused by your use of the "m" prefix when referring to an object. The prefix indicates that it's a memory variable. Object's, especially one's that are already in existence, aren't memory variables. So don't refer to them as "m.This" or "m.ThisForm" etc. There's no good reason to do so and as we can see from your posts, plenty of reason not to.
George

Ubi caritas et amor, deus ibi est
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform