It was not intentional. Honest... The reason I said it was interesting was because I had this expectation that the scope of a WITH clause would behave more like a local reference as opposed to a private reference. I didn't have any particular reason to think that way; I just did.
Mike yearwood wrote: > Hi Richard > > >> From: Richard Kaye <[EMAIL PROTECTED]> >> Subject: Re: Interesting WITH...ENDWITH behavior >> >> That must be it then. So WITH...ENDWITH stays in scope across methods >> further down the stack. >> > > I wouldn't call that interesting. Talk about breaking encapsulation! > If you put a .Property in a method by accident and a dangling > WITH...ENDWITH enables that .Property to operate, who knows what will > happen. > > Mike -- Richard Kaye Vice President Artfact/RFC Systems Voice: 617.219.1038 Fax: 617.219.1001 For the fastest response time, please send your support queries to: Technical Support - [EMAIL PROTECTED] Australian Support - [EMAIL PROTECTED] Internet Support - [EMAIL PROTECTED] All Other Requests - [EMAIL PROTECTED] --------------------------------------------------------- This message has been checked for viruses before sending. --------------------------------------------------------- _______________________________________________ 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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
