Ted, >...While it's true you can use an lSuperUser_Access method to extend this, why hide the possibility that code fires when you can code a method in the first place?
My usual approach is to work through methods instead of properties as much as possible. This is perhaps due to working quite often with "stateless" components where you can't rely on the value of a property outside the lifetime of the method call. This doesn't necessarily apply in this specific case, but when faced with a toss-up between property or method, I usually choose method, leaving more latitude for changing the implementation without affecting the interface. >Good discussion, thanks for asking. I agree. I enjoy this type of discussion very much. It's especially interesting to revisit some of these issues after wrestling out some real-life design issues in a variety of systems. David Stevenson -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.7/411 - Release Date: 8/7/2006 _______________________________________________ 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.
