Dave ... Andy ... I've gone the extra step and ...
RELEASE oButton_A After REMOVEOBJECT. ... CMA! Best, Francis I. Coppage, Jr. -----Original Message----- From: Dave Crozier [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 4:34 AM To: [EMAIL PROTECTED] Subject: RE: .removeobject Andy, I've had no problems at all apart from one potential Gotcha. ? type("oButton_A") && Returns "U" _Screen.AddObject("MyButton","CommandButton") _Screen.MyButton.Visible=.T. oButton_A=_Screen.MyButton ? Type("oButton_A") && Returns "O" _Screen.RemoveObject("MyButton") ? Type("oButton_A") && Returns "O" but should return "U" Beware because removing the button object does in fact remove the button but leaves the oButton_A as type "Object" which could lead you to assume that the object is still present even though it is no longer in scope. Ideally VFP should either make type("oButton_A") into null or "U" (ideally) or revert it back to the undefined VFP type of "L". Other than that I've not come across any other quirks. Just take care. Dave Crozier _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
