QUOTE (Jeff B. @ Jan 19 2011, 12:22 PM)

So we're talking about two different things.
One is the list of employees. The list is being stored in a "value list", basically "inside" the combobox control. Consider creating a new table to hold those, and pointing the combobox at the table instead. Managing a value list can get problematic over time.
Yes, this is accurate. Will that table be linked to the field in the other table, should I go this route?
QUOTE (Jeff B. @ Jan 19 2011, 12:22 PM)

The second thing is storing records about something, with one of the fields in those records being which employee.
Correct.
QUOTE (Jeff B. @ Jan 19 2011, 12:22 PM)

Describe the table structure of that table, in which an employee is just one of the facts ...
Simple table. Ten fields.
Employee - Text
Position - Text
Month - Text
Day - Date/Time
DisciplineType - Text
Description - Memo
Level - Level
Points - Number
AccumPoints - Text
TempStat - Text
QUOTE (Jeff B. @ Jan 19 2011, 12:22 PM)

(... and where does the "builder" come in? Are you doing this in design mode, for a form?)
Yes, pulling it in design mode for a form.