[AccessD] Code Help Please

I didn't feel the earth shake!?!  That usually only happens when JWC and
I agree! ;)

I do some side work with a fellow that had a real bad habit of creating
complex field names.

For instance, if he had an Incident Number in tblIncidents, he'd name it
I_txt_pk_Incident_Number.  And if that field was in another table, such
as tblInsuranceResult, it would be I_txt_fk_Incident_Number.  'I'
represents that it's in the incident table, txt for text data, pk or fk
for primary key, foreign key, and then the actual field name.  Seems
very practical until you get to the level where you write the SQL by
hand....and then it is just a complete pain in the neck! ;)

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Thursday, March 06, 2008 4:36 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Code Help Please

Field names are the one place where I most emphatically do NOT use
naming conventions.  It has always seem unnecessary to me, since it does
nothing for your code, the place that naming conventions come into their
own.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Thursday, March 06, 2008 1:22 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Code Help Please

I concur.  I use a 'common sense' name for field names (ie, FirstName,
instead of a prefixed name, such as strFirstName), because I use
variable types for my variables (strFirstName), and control types for my
controls (txtFirstName).

Though I do deviate from that method when it comes to my class objects.
If I create a Person Object, it would have a FirstName property, not a
strFirstName property.

Drew
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.