On Apr 12, 1:53 am, Jack Jackson <jjack...@cinnovations.netwrote:
On Fri, 11 Apr 2008 13:59:23 -0700 (PDT), nottarealaddr...@hotmail.com
<snip>
When you have a public property with a private variable to hold its
contents, you can't name both the same. With C# you can make their
case different. With VB you can't do that because VB is case
insensitive, so one common way to deal with this is to put m_ on front
of the private variable. There is nothing magic about using m_.
Gotcha! It's the same as prefixing the Booleans with bool, Integers
with int, etc.
Hopefully without getting too personal, I'm sitting here after all my
housework is done, showered, TV off. I'm physically relaxed and I've
had time to wrap my head around the code sample you provided, tweaked
the names to my application (it makes more sense to me when used in a
particular application). It worked like a charm. I coded it, and I
started to enter a line of code to test it. When I got to
"Me.Aspect1.Read =" , Intellisense popped up with a little choice menu
consisting of True and False--exactly what I was looking for. And this
concept will be so useful for other things.
All I can say is SWEEEEEEEEEEEEEEEEEEEEEEEEEEEEET! (And I've never had
the urge to say that before!)
This is a high-profile application and the first one I'm doing in
VB2005. You are going to make job so much easier and now I feel I can
get this project into roll-out before my surgery as my boss wants.
(New hip, so I'll be out maybe 4-6 weeks.)
Thank you for taking the time to walk me through these new concepts!
-Scott