[AccessD] Need help with a combobox issue

The problem with that practice is that Services.Name in other
circumstances will return the name of the Services table, not a
reference to a column in Services.  It might work or not, depending on
the situation, and it's virtually guaranteed to bite you somewhere along
the way.  In general it is NOT a good idea to use names that are already
built in as function names or properties.  Name and Date are two
examples of that.

Charlotte Foust


-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com] 
Sent: Monday, March 28, 2005 8:47 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Need help with a combobox issue


I agree with you on the usefulness of UNION queries, and just want to 
add one comment which really has little to do with this thread, but 
concerns maximizing the utility of UNION queries.

I commonly see in other people's code such column names as ServiceName, 
ProductName, etc. I never name columns in this way. Instead I call both 
columns Name, and distinguish them with the tableName prefix: 
Services.Name and Products.Name. That way UNIONs are effortless, while 
the tableName prefix sidesteps ambiguity.

My $.02. :)

Arthur.

DWUTKA at marlow.com wrote:

>Glad to help.  Gotta love those UNION querries, they make life soooo 
>much easier!
>
>Drew
>
>  
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com