"Larry Linson" <bouncer@localhost.notwrote in
news:sgGfh.8252$Q36.8058@trnddc08:
Quote:
"Keith Wilby" <here@there.comwrote in message
news:457ec010$1_1@glkas0286.greenlnk.net...
Quote:
>"Larry Linson" <bouncer@localhost.notwrote in message
>news:ggkfh.4641$bj5.3024@trnddc07...
Quote:
>>"MLH" wrote
>>>
>The Me object in A97 HELP is associated
>with forms.
>>
>I've used Me.Name with success in a report's
>Open event code successfully. However, I
>seem to recall occasions where use of Me in
>report objects could present problems. Anyone
>know more about this subject?
>>>
>>I cannot recall ever having a problem using the "Me" shortcut in
>>a Form's module, or a Report's module -- but those are the only
>>places it applies.
>>
>I'm happy to be corrected but I thought that the Me keyword
>referred to the current class module and would be available in
>custom classes.
>
I've never used it that way... perhaps it can be, if you have
defined Properties and/or Methods for the custom class to which
you wish to refer.
Yes, Me refers to the current class module, which can be a form
module, a report module or a standalone class module. I would never
refer to properties or methods of a form/report without the Me
identifier, so I use the same practice in standalone class modules,
using the Me object whenever I want to use one of the methods or
properties of a class module within itself. It seems obvious to me
that this is the most consistent way to code, and that there's a
reason why it works exactly the same in all three contexts.
--
David W. Fenton
http://www.dfenton.com/
usenet at dfenton dot com
http://www.dfenton.com/DFA/ 
