how do I save to a table from a form combo box?

I created a few tables. and with the use of combo boxes, I was able to
standarized the records that we used at the office.
Here is my problem.. I set up a table called Employee_Info which shows:
Employee file number, employee name, and employee last name...
what I want to do is just select the file number and let the other boxes
filled the blanks with the data. While on Form view... everything is
displayed accorndingly, but they are not being saved on the main table where
I want them to be stored

Need some more detail, please.
Do you have combo boxes for all 3 fields?
Are the comb boxes bound to fields in the form's recordset?
Is this for adding new records?
Does the user need to see the employee's name, or just the file number?

I know what is wrong, but I need to know all the above information to
provide you the correct answer.
--
Dave Hargis, Microsoft Access MVP


"Sasha" wrote:

I created a few tables. and with the use of combo boxes, I was able to
standarized the records that we used at the office.
Here is my problem.. I set up a table called Employee_Info which shows:
Employee file number, employee name, and employee last name...
what I want to do is just select the file number and let the other boxes
filled the blanks with the data. While on Form view... everything is
displayed accorndingly, but they are not being saved on the main table where
I want them to be stored

On Tue, 24 Jun 2008 10:28:00 -0700, Sasha
wrote:

I created a few tables. and with the use of combo boxes, I was able to
standarized the records that we used at the office.
Here is my problem.. I set up a table called Employee_Info which shows:
Employee file number, employee name, and employee last name...
what I want to do is just select the file number and let the other boxes
filled the blanks with the data. While on Form view... everything is
displayed accorndingly, but they are not being saved on the main table where
I want them to be stored

If you're trying to copy the employee first name, last name (surely you don't
have "Bill Jones" in one field and "Jones" redundantly in another field, do
you!?) from one table into another table... DON'T!

Relational databases use the "Grandmother's Pantry Principle": "A place - ONE
place! - for everything, everything in its place". The employee's personal
data (name, birthdate, etc.) should exist in the Employees table, *and noplace
else*. The only thing you need in other tables is a "foreign key" - an
employee file number, it seems - as a link to the employees table.

--

John W. Vinson [MVP]