Combo Box OR Lookup Table OR Subform?

G

GaryS

Design question: I'm still not clear on when to choose a
(multicolumn) combo box, a Lookup table, or a Subform when
dealing with displaying (and updating) data from two
tables in a one-to-many relationship.

I have used all three techniques more or less
successfully, but I'm sure there are some design
guidelines I don't know about.

Help from the gurus would be appreciated!
 
C

Con Giacomini

I don't think table Lookups are of any special value.

A multi-column combo box is very useful in helping to find the correct
record for selection. For example if the combo box is filled with first and
last names, an additional column to display 'city' might be desirable to
discern the difference in records where you have duplicate first and last
names (it happens). The next issue is whether the 'additional' columns are
needed only for selection or for display on the form. To have them shown on
the form you need to use the COLUMN property.

In a one-to-many relationship where you have, for example, multiple
transactions pertaining to a single entity, the use of a MainForm/Subform is
the way to go.

Con Giacomini
 
G

GaryS

Thanks, Con.

SO, let's see if I can summarize:

1. If I'm trying to select the proper "X" for further
processing (incl. updating), use a combo box whose source
contains a list of the "proper" values of X.

2. If I just want to display a set of records related to
the basic form record, use a Subform.

Gary
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top