Use drop down to fill one form field and other fields auto filled

[MentalDrow]

Howdy,

I've tried searching this posting area but have been unable to phase the
search in a way to get relevant results so please forgive me if this is a
repeat.

Here's what I have and if you need further information to assist me, I'll be
happy to provide it since it's to my own benefit.

I have a database I use to track multiple things but the two tables I want
to interact.

Table A contains a list of workstations sorted according to the machine
name. The information on it ranges from the MAC Address, User, Room # and
phone number of the user.

Table B is a list of monitors sorted according to their serial numbers. The
information ranges from the serial number. User, Room # and phone number of
the user and other information. I've created a drop-down list from the
workstation name of Table A.

What I want to know is how do I set up the relationships or other things so
that when a workstation name is selected using the drop-down list the other
information (User, Room #, phone number etc) is automatically filled in on
Table B.

Thanks in advance for your help.

 

[mscertified]

Some questions, how are the 2 tables related? Does each room have just one
monitor and machine or many? Does each user have just one monitor and machine
or many? Does each workstation have just one monitor? Do all monitors have a
workstation? Do all workstations have a monitor? Are workstations or monitors
ever moved to different rooms?

I'd say you most probably need the workstation id in the monitor table. You
would link based on this id. This way if you ever did need a second monitor
for a workstation, it would still work. You would just have a second monitor
record with the same workstation id.

Dorian

 

[John Vinson]

What I want to know is how do I set up the relationships or other things so
that when a workstation name is selected using the drop-down list the other
information (User, Room #, phone number etc) is automatically filled in on
Table B.

It's almost certainly WRONG to store this information redundantly in
TableA *or* in TableB.

It should be stored in a User table; TableA and TableB should store
only a user ID.

John W. Vinson[MVP]