Understanding relationships and auto populate...

[richardcasci]

It may help to understand what kind of tables I currently have in Access 2010....

I have an employee table that shows all employees and some basic information about each of them. This table has an employee ID field that is not an autonumber but it is unique to each employee (10004928).

I have other tables that also use that same field and I want the first and last names to auto populate based on the main employee table. These other tables are tracking OT and Vacation time used.

How do I make the later tables auto populate the name fields when you key the employee ID???

I have relationships set up, but I do not know if that helps....

 

[spikepl]

You don't make those tables autopopulate. Because you don't duplicate info in a normalized db. You want to see names from another table use a query.

 

[richardcasci]

You don't make those tables autopopulate. Because you don't duplicate info in a normalized db. You want to see names from another table use a query.

The Overtime and Vacation tables will be used to key daily information about different employees. To simplify data entry i wanted to be able to key the employee ID and say that for 05/03/2012, employee X worked 4 hours of OT.


The attached picture is just the basic form that I am looking at. Once the EmployeeID is selected, I want the name fields to automatically go in.

 

[spikepl]

It has nothing to do with tables. That is why you have relations, so that data stored in another table with a given key can be displayed in a query together with data for your table in question.

DO a tutorial on Access queries (google it), or open the query designer and play with dragging fields from both related tables in the the design grid.

 

[richardcasci]

It has nothing to do with tables. That is why you have relations, so that data stored in another table with a given key can be displayed in a query together with data for your table in question.

DO a tutorial on Access queries (google it), or open the query designer and play with dragging fields from both related tables in the the design grid.

I will do some more research. I just thought that if I have a user keying this information in, they will want to see the name that they are keying it for.