Hi
A LookUp (or Masterfile) table is generally used with a ComboBox to select values to ensure consistency and to save the user having to type in the same things each time.
There are generally 2 ways to do this:
1) To create a seperate table that comprises of a code and a description of that code.
or
2) To have the ComboBox "self generate" the list itself based on what values are typed into the field by the users.
1st option
This is generally the best way to go as there may be a point in the future where a "description" may change. For example, if you had a list of doctors you may have "Dr Judith Brown" she may get married and become "Dr Judith Smith". If her code is D01 then that is what is stored in the main data table and whenever that code is referred to, the latest name will appear. The "bound" field to the main table will be the code field.
2nd option
This is useful where you are unsure as to the number of items to put in the "lookUp" table. For example, patient diagnosis - you could have thousands in a lookUp table but only use 10 or 20. So self generating a list of "actual" diagnoses used is more effective. Plus these are not likely to change, as mentioned in the above option.
Personally I always try to go for the first option as any changes to the description will automatically be reflected in any reports/queries. Obviously, the code must remain the same.
As for getting the text or description to be produced on a report or form rather than the stored code, use the DLookUp function.
Hope this helps, there may be others with differing views but I generally find the above works ok.
Col
