Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ASSIGN bug : was fixed in VFP8 ?
Message
 
 
To
24/09/2003 21:25:48
Gerry Schmitz
GHS Automation Inc.
Calgary, Alberta, Canada
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00831739
Message ID:
00832073
Views:
39
Gerry,

Don't get me wrong, Access/Assign are great additions to the language. In all the code I've done in VFP I'm hard pressed to come up with a use case where using them on native properties is required. I imagine most code that is being hooked to form.Width or form.Height would be better off just put in the Resize event. A/A work as expected with custom properties.

I don't have a theory about why assign is being triggered because of the access on the native properties, it's buggy behavior IMO.

>Yes ... I do pretty extensive testing. It does seem the problem is limited to certain properties. I just have to revisit them all, that's by biggest beef. I "thought" that everything was working fine .... I just can't be sure now and have to retest to be sure.
>
>(A craftsman is only as good as his tools, and when he looses confidence in his tools ...).
>
>Like you, I should have stayed away from ACCESS/ASSIGN, but where I did use them, they had seemed ideal (at the time).
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Previous
Reply
Map
View

Click here to load this message in the networking platform