validation as an alternative to lookup fields?

[LF]

I understand that for end-user performance reasons it is recommended to use
lookup controls within forms to lookup related info between tables as opposed
to lookup fields within tables. Does the same hold true for a small Value
List Lookup to enforce consistent input within a single table?

If so, is it ok to use Validation within table fields as an alternative?
For instance, if the Validation Rule Property is set to ...
= "Q" Or "C" Or "D" Or "R"
and the Validation Text Property error message is ...
Only single characters are allowed where...
Q = Question, C = Clarification, D = Deficiecy, and R = Request

Is it better to also set up a single-select combobox in the form where the
first of 2 columns is bound and 0 width, and RowSource is set to following?
"Q";"Question";"C";"Clarification";"D";"Deficiency";"R";"Request"

I'm thinking doing both will ensure intended input if entered directly in a
table or through a form. Or is doing both redundant for no reason? Or will it
also slow performance?

Your insight is appreciated!

 

[Damian S]

Hi LF,

If you have a combo box set up that gets its data from a lookup table and is
set to "Limit to List = YES", then you have the effect of only allowing what
you want, with the flexibility to add new items to choose from by simply
adding them into the lookup list table.

Damian.

 

[Duane Hookom]

I prefer to use small lookup tables to create combo boxes on forms. I don't
allow users to enter/edit data directly in tables or queries. Lookup fields
in tables are to be avoided.

I don't use value lists since list are rarely ever static.