Filling fields based on lookup field instead of combobox

[hensleyj6]

What I am trying to do is I am working on a small project to keep track of employees time.
I have two tables one for employee information and another for saving the times worked.

I'm trying to get the employees first name, last name, from table a into fields for saving with in and out times into table b.


I want to be able to have them enter their ID number, and have it populate the above fields automatically so they can be saved into an entry in table b.

I am currently experimenting with using a combobox at the moment but what i want is to use a text field because I will have a barcode scanner where the ID will be scanned and then afterwards I want it to populate those fields and then from there the time/date is saved into an entry with the information.

Below is what i have going using the combo and filling the name based on it. but as i said earlier I would like to use the scanner instead.

EID.SetFocus
EID.Text = Combo21.Column(0)
First_Name.SetFocus
First_Name.Text = Combo21.Column(1)
Middle_Name.SetFocus
Middle_Name.Text = Combo21.Column(2)
Last_Name.SetFocus
Last_Name.Text = Combo21.Column(3)

[RuralGuy]

You do realize that having the ID in a field allows you to user a query and show both tables and if they were one, right?

[hensleyj6]

Honestly, no. using access at all is new to me, what i have gotten to this point is from other tutorials and old forum answers. The idea for what I am wanting to do came from a friend who suggested doing this to help instead of doing what i was doing which was manually filling a spreadsheet and using that to track time. Since we have such a small number of people on our payroll they said it would work, and then just print a report like my spreadsheets and i can purge it when its getting too big.

[RuralGuy]

One of the *big* powers of MS Access is queries with joins. The idea of an RDBMS is that the actual data *only* exists in one table and everyone looks for it there. Joins make that a snap. You also create your relationships and enforce referential integrity to make sure everything stays properly layered.

[RuralGuy]

Here's a link to a slew of data models showing the relationships. It may give you a few ideas about the structure of your database.
http://www.databaseanswers.org/data_...all_models.htm

[hensleyj6]

ok great thanks for the link and information I will look at that all. I have been looking for examples as well that i could use, do you have a place where I can find those? I have been searching but I am having no luck as far as finding anything helpful.

[RuralGuy]

Have you looked at all of the templates that come with Access?

[ssanfu]

You might want to work through these tutorials....
http://www.rogersaccesslibrary.com/forum/forum46.html