Why not use lookup wizard in table design?

[Ursula]

Hi,
I've been reading through the posts here trying to find a
solution to my problem and I was wondering why the lookup
feature in the table design has such a negative reputation?
Should I not be using it when I set up my tables? I AM
having a problem updating records as certain fields won't
accept duplicate values (they're the many in the
one-to-many relationships). I changed the index properties
to accept duplicates, or even to NO to see if that would
work but it hasn't. These problems are in a test subform
with a promary form for Employee records.

Any suggestions?
Thanks
Ursula

 

[Steve Schapel]

Ursula,

As a partial answer to your question about lookup fields, see
http://www.mvps.org/access/lookupfields.htm

This may or may not have anything to do with the problems you are
experiencing. Could you please give a bit more information about the
the fields in the Employee table, the "many" table, and what is
actually happening?

- Steve Schapel, Microsoft Access MVP

 

[Albert D. Kallal]

Well, I think the bad rep for the lookup is bit over blown. If works for
you, then that is why the feature was added.

For many people the lookup feature makes things easy.

As for your one to many problem. Hum. Can you get "any" one to many
relationship to work?

I would double check what the link master, and the link child settings are
for the sub form. This two fields tell ms-access what value to set in the
fields used for the relationship.

so, bring up your form in design mode,a nd then click on the sub-form. You
then want to look at the data tab in the properties sheet. Often, it picks
up "id" and "id" for the link/master fields. Likely these are the wrong
field names.