On Aug 31, 4:55*pm, "Chris O'C via AccessMonster.com" <u29189@uwe>
wrote:
Quote:
Most people use the second example. *Less typing.
>
Chris
Microsoft MVP
IIRC (I don't have the reference anymore so don't ask), Microsoft
advocated using .Value instead of relying on the default property of
the control based on the fact that they do not guarantee that the
current default property in a given version will be the same as the
default property in a future version. I think they even gave an
example where the default property changed from .Value to something
else from one version to another. Something like the second example
could fail, or worse assign a completely wrong value without giving
you any indication that something is wrong. Subsequently, I try to
include the .Value where appropriate. A bonus is that if IntelliSense
picks up the .Value in the list, you likely didn't spell the name of
the control incorrectly. Of course some people rely on the compiler
to discover that :-).
James A. Fortune
CDMAPoster@FortuneJames.com