Auto-Populate ERROR!

valsanch

Registered User.
Local time
Today, 14:58
Joined
Mar 21, 2013
Messages
11
I read a link on auto-population in a form. I thought I followed it to a "t" but my field is not being auto-populated. I have several tables, however, just two specific to what I am trying to do. I feel so close to a solution. I have a table called, "tblActivity" and "tblSimulators". I created a form based off of "tblActivity" and I want to add a field called "Fidelity" on that form. That field is housed in "tblSimulators". I have built a relationship between the two tables. The field connecting them is called, "SimulatorType".

Initially, I had "Fidelity" on the "tblActivity" but I erased the column since that data was housed in "tblSimulators". I added a text box to my form and called it "Fidelity". In the combo box for "SimulatorType", I added the field "Fidelity" in the row source query grid. I then went to the properties for the new text box and added, "SimulatorType.[Column(1)]" to the Control Source. When I go to form view and tab through the form, I read, "#Name?" and it does not auto-populate with the corresponding fidelity of the simulator. Any ideas? Thanks!!!
 
Drop the square brackets:
SimulatorType.Column(1)
 
One step closer! So, the error is no longer there but now the field is populating the field with the simulatortype and not the corresponding fidelity. So for example when I choose "TraumaMan" from my Simulator list. The Fidelity field will populate with "TraumaMan" and not the fidelity of the simulator which would be "LF". I am not very saavy with Access but my Simulator combo box is reading the control source from my "tblActivity" but the row source is reading from "tblSimulators". Could my sources be the reason for this? Thank you so much for your help.
 
As posted on your other thread, you need =:

=SimulatorType.[Column(1)
 
Hi PBaldy and Galaxiom, I found the problem. I have no idea why, but I had to put 2 instead of 1 in the column() function. Now all of the fidelities are auto populating and are correlating with the simulator type. I find this odd though because my row source only has 2 fields selected and I thought the first column was always considered "0"...odd, but it now works. I thank you both for your help!
 

Users who are viewing this thread

Back
Top Bottom