Me! vs Me.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

just curious.....i see code using either of the above "Me!" or "Me." when
referring to forms in code.

what's the difference between using the "!" or "."?

thanks, and this is definitely NOT an urgent question...
;-)
 
thanks - silly me, i looked for Me! and Me.

i didn't try "! vs ."

and definitely didn't think to look for "bang" or "dot"
 
janaki said:
just curious.....i see code using either of the above "Me!" or "Me."
when referring to forms in code.

what's the difference between using the "!" or "."?

thanks, and this is definitely NOT an urgent question...

Here's my stock answer on the subject:

--------- BANG (!) vs. DOT (.) ----------
It's not so much a question of one or the other being "proper syntax",
but that they mean different things that nevertheless almost always give
the same result. As I understand it, the bang (!) notation specifically
denotes that what follows is a member of a collection; in this case, a
member of the form object's default collection, the Controls collection.
The dot (.) notation denotes that what follows is a property or method
of the preceding object. That would logically make the bang notation
"proper" and the dot notation improper.

But wait. Wherever possible, Access makes the controls on a form and
the fields in its recordsource all available as properties of the form.
It also makes the fields of the recordsource available via the bang
notation. I'm not sure exactly how it does this; maybe if a name is
not found in the Controls collection it checks the Fields collection of
the form's recordset as a fallback position. So for most practical
purposes Me!ControlName and Me.ControlName evaluate to the same thing,
and the timing tests I've seen suggest that there is little to choose
between them as far as execution efficiency is concerned. I seem to
recall that there is a very slight difference, but I can't remember
which way the advantage lies, and it's not much. There's a coding-time
advantage, however, to using the dot notation, as it makes the
"intellisense" dropdown lists available. That's a strong argument for
using the dot notation, in my book.

But wait again! I said above that Access makes the controls available
as properties "wherever possible". There are cases where it can't do
that. Specifically, it can't do it when there is already a property of
the same name as the control in question. For example, if your form
"Form1" has a control or a field foolishly named "Name", currently
displaying the value "John Doe", then executing this statement in the
form's code module:

Debug.Print Me!Name, Me.Name

will print

John Doe Form1

in the Immediate Window. So you must be careful not to use any reserved
words or built-in properties as names for your controls, if you want to
use the dot notation to refer to them. But then, you should avoid doing
that anyway, as it tends in general to confuse poor Access.
 
i love this answer, Dirk. it would be great if it were available on a
website, so we all could refer people to it. just a thought... :)
 
tina said:
i love this answer, Dirk. it would be great if it were available on a
website, so we all could refer people to it. just a thought... :)

Thanks, Tina. One of these days I'll get around to putting a few tips
and articles up on my website. It seems to be the done thing.
 
Back
Top