Hi David

>Mike,
>
>When I changed the click method Fabio orginally posted to change the m.this to just this (see message http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~2,15,894781 ) the C05 stops occuring. I believe Bob posted the same solution on another branch of this thread or the other similar thread.
>
>Please note that I'm not saying that the current C05 behavior should remain. Just that there is currently a way, one that has been in VFP since the day VFP3 shipped for that matter (ignoring that access/assign did not appear until a later version), to write the code Fabio is wanting to do without running into a C05.
>
>So this ends up being a [The doctor says: "Well don't do that"] solution; while another set of surgeons sew shut the hole that allows the painful code to be written in the first place. *g*
>
>>This is not the first time in this thread that m. has been mentioned. The text above suggests m. is making no difference. It seems premature to blame m. for the C5's in this thread. Yes, I'm probably biased. Does the c5 happen 100% of the time? Does it fail to happen 100% of the time without m.? If you cannot say yes to both of these, then you should rephrase. m.This may cause c5's in certain unusual circumstances.


Understood. Bob did confirm the c5 happens m. or no m.. So, IMO m. is not related.