Ok - that makes a little more sense. Your first post did say TWO combo boxes..
Make the source for the first combo box a query that grabs the ID and the NAME. Set the combo box to have TWO columns, and make the ID the bound column. Set the column widths to an appropriate width greater than 0 inches for the ID, and 0 (zero) for the name (the name will not be visible in the drop-down).
In the AFTER UPDATE event of the combo box, set the TEXT box to contain the 2nd column of the combo:
Me!TextBox = me!ComboBox.Columns(1)
I guess my question now is, why are you using the ID in the first place? Is that the value that the user will know/have? Wouldn't it be easier to just build the combo box with the NAME itself? A drop down of alphabetical names is generally much easier to use than one of numbers, unless your users have ONLY the numbers, and need to get the names.
In any case, the additional columns of a combo box can be referenced using the COLUMNS property, with the number being ZERO based - the first column is Columns(0), the second column Columns(1) and so on. Setting the column width to zero is an easy way of including multiple values on a 'line' of a combo box, but keeping them unseen by the user. You can then reference them later on.
Jim
Me? Ambivalent? Well, yes and no....
Another free Access forum:
More Access stuff at