Database Structure Question (Access2000)

[ahmun]

I have a table (access2000) that stores employee information, and it uses lookup tables to classify what craft, region, business unit, etc. that the employee is in.

in these lookup tables, should I have some kind of unique primary key? or is that not necessary to the functionality of databases in general or Access?

Thanks

 

[svanels]

Of course you must use an unique primary key.

Let say you have in your craft look up table the following

type skill
---------------------------
carpenter 2nd grade
welder 2nd grade
welder 1st grade
mechanic 3 rd grade


If you have a look-up on type, which welder the database must asume? Your reference must be unique S. van Els
SAvanEls@cq-link.sr

 

[ahmun]

In the case where I have customized lookup fields, I can see a need for having a primary key to make my lookup table entries unique, but how about in the case of a lookup for... say... State? as in address info of an employee?

Should I have a seperate lookup table? or just define the combo box with the state letters?

 

[svanels]

If you have information that is not likely to change, use the validation option in the field. In case of state I would use a look-up table. A combo box can be filled at run-time from a query. S. van Els
SAvanEls@cq-link.sr