[AccessD] Naming Conventions

LOL.  I'm reading a book called 123 magic to teach parents a method of
establishing discipline for small children (ages 2 to 12 - my 3+ year old in
this case).  The theory behind the book is that the child will do ANYTHING
to get a reaction of any kind, for the simple reason that it gives them a
feeling of power when they are really pretty much powerless.  Any time you
argue with the child, the argument can not be won simply because the POINT
of the argument is not winning or losing, being right or being wrong,
learning something new etc. but just that the argument itself gives a
feeling of power.  They are causing something to happen.

An interesting perspective.

JWC

-----Original Message-----
From: Charlotte Foust [mailto:cfoust at infostatsystems.com]
Sent: Friday, August 13, 2004 12:13 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Naming Conventions


That's exactly the point, Drew.  If FirstName is a class, then that
statement is invalid.  But you can't tell by looking at it, now can you?
Are you suggesting that you look at the way something is used in code to
determine what kind of thing it is?  You DO turn on Option Explicit
don't you??  Have you have *NEVER* typed something like 

Set Whatever = 5 

or 

Frm = Forms!MyForm  

Charlotte Foust