jwcolby
jwcolby at colbyconsulting.com
Thu Mar 6 22:05:40 CST 2008
LOL, I find nothing wrong with differentiating the Name field in the employee table from the Name field in the company table. Works for me. I have done too many Search and Replaces on databases where there were 47 Name fields (or even worse ID fields). Every table has an ID field named... you guessed it, ID. Which ID are we talking about here? Oh... THAT ID... Two hundred tables each of which have an ID field. Hmm..... Yep, EM_ID is different from CO_ID and EM_Name is different from CO_Name. Naming conventions are about what works for you, and what works for me is knowing which ID field I am looking at without having to spend hours examining 4768 instances of ID by hand in my Search and Replace. 8-) John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, March 06, 2008 6:05 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Code Help Please Hmmn .... I wonder who that could be? As I recall, JC likes to create field names that identify their tables, etc. Could it be .... NAW!! Of course not. 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 3:00 PM To: Access Developers discussion and problem solving Subject: Re: [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. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com