Concept elusion

[RustyRick]

One concept that I just can't seem to get my head around and make work.

I have a 2 table data base. Simple.

1) Employee c/w a UnitNBR and a "Site" field.
2) Daily Work Log for each employee.


I have an "employee ID" field, who is assigned a piece of equipment "Unit Nbr" and resides at one of our "Sites".

I want to be able to enter the employee's ID and have the form populate the fields for "Unit Nbr" and "Site".

What's the right approach. I can make queries work and Lookups work. But I don't want to stop in every field to enter data that relates to thee employee. I know it's simple and Access can do it easy. This old timer is loosing it.

:banghead::banghead::banghead:

 

[CJ_London]

Not quite clear what you are trying to ultimately do so I presume the form is to complete the daily work log

On the form, have a combo box (called cboCtrl) with a recordsource that selects all the details you want to populate on your form. Set the number of columns to include the number of fields selected

In the after update event of combobox put the following (change names to suit)

me.field1=cboctrl.column(1)
me.field2=cboctrl.column(2)
etc

 

[RustyRick]

In my "Log Book" table I'd like to be able to enter the "Employee ID" and have Access populate the fields "Unit#" and "Site" which are very consistent and rarely change. Therefore I have those 2 data items in the "Employee" table.

I can make a combo box or list box and click on the selection. That's hugely time consuming when I have to enter over 150 entries per day.

So I'm sure that Access will allow me to make a relationship between the 2 tables based on the key "EmployeeID". And when I enter that it automatically populates "Unit #" and "Site".

So this is strictly a "Data Entry" form and I don't want to see any historic data for the employee. :banghead::banghead::banghead: Thanks