View Single Post
  #3  
Old November 19th, 2008, 06:39 PM posted to microsoft.public.access.tablesdbdesign
TravelingHT
external usenet poster
 
Posts: 35
Default Comboboxes or Conections for Look up Tables and Data Tables

Dear Clifford:

So I hear the info about the customer. I will take that onboard.

Thanks for the response, to help me I need the why of it. Why if I am using
a combobox to create the list of choices and that list of choices has a limit
to list property. Then I am OK with just a combobox, and no link between the
tables.?

Under what circumstances will the above senario cause me a problem?

Is what I am asking just not that improtant, is there realy no big difference?

Yours truly.

Traveling Tech.



"Clifford Bass" wrote:

Hello,

You definitely create the relationships. This will make sure your
table only contains valid data such as real state codes. If you do not,
someone could enter invalid codes. The combo box is a convenience for the
user. Use it if it helps the user. Don't use it if it is a hinderance.

My $0.02 worth,

Clifford Bass

"TravelingHT" wrote:

Dear All:

I have a question. Reading about lookup tables, (e.g. tax rates for
different states) should I connect these lookup tables to my Data tables
(e.g. Customer Line Item Invoice Table) in my Relationship window or should
I just created a combobox with a record source being the tax rate table and
have no relationship defined in my "Relationship" window?

What is the difference between these two aproaches and what are the
advantages.

Thanks in advance.

Traveling Tech