Links, Queries, and Forms

J

Jack Marks

Maybe somebody can give me a simple answer to this:

I have 3 tables. I was able to link them all, so that part is done. Now
I want to make a form with most of the data from the 3 tables. AND, I want
some fields on the form to be the lookup type, where I get a choice from the
data in the tables. So my questions are 2:

1. To feed the table do I make a 4th table, or do I make a query?

2. Where do I put the lookup data, in the table, or in the query? If a
table, does it go into the base data table or into the consolidation table?
 
D

Douglas J. Steele

1. I'd recommend a query.

2. Lookup data typically is set as the Row Source for a combo box, with the
combo box bound to the appropriate field in the underlying record source for
the form.
 
D

Douglas J. Steele

I have no idea what you mean by "do the lookup stuff on the query".

I suggested you create a query to use as the Record Source of the form. I
also suggested that if you need to do lookups, you create comboboxes on that
form, with each combobox having the appropriate Row Source. By binding the
comboboxes to the appropriate fields in the query, you can update the value
stored in the tables, but you're not doing "lookup stuff on the query" as
far as I'm concerned: you're doing lookups on the form, and updating the
underlying Record Source object.
 
J

Jack Marks

If I use the lookup function on fields on the Query, repeat Query, that
lookup function can then be carried over with no change onto the Form that
uses the query, regardless of whether I decide to make a combo box or not.
I think. Isn't that correct? I want to always be able to look up the
"name" rather than any other way of finding it. Then, if I do decide to
use a combo box, I can still ADD to the list by continuing to use the looked
up field. So, if I have a Committee List, with the member's names, I can
add a member by clicking on the next, blank, line, click on the down arrow
lookup thing, look at ALL the members, and just select the name I want. Is
there something inherently wrong with this approach?
 
D

Douglas J. Steele

To be honest, I don't know. I never bother with lookup functions on tables
or queries, since you should always be using a form for input.
 
Top