Option Groups in a Table

[Lisa]

Is there a way to use an Option Group in a table, instead of creating a form
with unbound forms and have to create code to insert the data in the table?

 

[Duane Hookom]

You can create lookup fields in tables but this is generally considered bad
since data entry should be done from forms, code, queries, and NOT tables.

 

[Jeff Boyce]

Lisa

To add to Duane's observations, a lookup datatype field in a table means
Access stores one thing (i.e., the key value), but displays another (i.e.,
the looked-up value).

Unless you remember this, and everyone else who might use that table knows
(and remembers), there'll be confusion and trouble.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John Vinson]

Is there a way to use an Option Group in a table, instead of creating a form
with unbound forms and have to create code to insert the data in the table?

No. Why on earth not just use a bound form?

John W. Vinson[MVP]

 

[LurfysMa]

Lisa

To add to Duane's observations, a lookup datatype field in a table means
Access stores one thing (i.e., the key value), but displays another (i.e.,
the looked-up value).

Unless you remember this, and everyone else who might use that table knows
(and remembers), there'll be confusion and trouble.

So the Lookup feature should NEVER be used at all?

Suppose I have a table with a field named "Priority" that can have the
valuesd "High", "Medium", and "Low". Should I create tblPriorities and
put a link to the appropriate row in the field?

 

[Duane Hookom]

I would create a small lookup table. I ALWAYS assume lists will change in
the future.

 

[John Vinson]

So the Lookup feature should NEVER be used at all?

Suppose I have a table with a field named "Priority" that can have the
valuesd "High", "Medium", and "Low". Should I create tblPriorities and
put a link to the appropriate row in the field?

If you're using the Lookup wizard, that is EXACTLY what Access is
doing for you; it's then simply concealing the linking field from
view, and creating a relationship to the Priorities table and
concealing THAT from view as well... not to mention creating one or
two probably redundant indexes.

At least if you do it yourself, you know what's there!

John W. Vinson[MVP]

 

[Jeff Boyce]

"?Should?" If you want absolutes, ...

You'll find a lot of folks here in the tablesdbdesign newsgroup who
recommend against using lookup datatypes in table definitions. As my
response suggested, there are risks (confusion) with deciding to use lookup
datatypes.

Go ahead, if you're willing to do what you have to to mitigate the risk...

(and I agree with Duane and John ... I find it easier to create a lookup
table and make the connection explicit, and via forms. That way, I can
always add new items to the list, and no one has to remember that what you
see is NOT what you get.)

Regards

Jeff Boyce
Microsoft Office/Access MVP