If you are using DoDefaults I suggest using NoDefault in the methods
first to stop some of them running twice (when you call doDefault and
when the method closes). This seems to happen to some of the system
methods like unload.
However I think a better approach is to the 'Access' method on the Value
property. Then it is much simpler, downside is tracing what is going on
as you can't look at the value of your subclassed textbox in debug by
just hovering on it (as it is now a procedure that returns that value)
--
Michael Hawksworth
Visual Fox Solutions
[EMAIL PROTECTED]
www.foxpro.co.uk
_______________________________________________
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.
