Yep, I get it now. Whatever value is in there will get stored into table 1, but you want the drop down list they can select from to be loaded with all the values from table 2, right? I have to say, I'm not sure how to do that with bound controls since I try to stay away from using bound controls (I like to have more control over my database operations, plus there are performance issues to consider with that). I "think" (let me stress "think" here) that you can do this with two ado controls, each linked to the same database but different tables (table 1 and 2). When you load the form you can cycle through the table 2 ado control using the combo box's AddItem method to add the EmployeeNumber for each record in table two. The combo box itself is bound to the ado control for table 1, though. Does that make sense? Basically, you do a MoveFirst on ado control 2 (for table 2) and loop doing a MoveNext until you are at EOF (or whatever the end of the records is known by in the ado control). For each of those records you say ComboBox.AddItem(EmployeeNumber) and off you go. You bind the combo box itself the same way as usual. Here's the caveat, I don't know if the list box is already pre-populated with the distinct values for the field it is bound to, so you may have to remove those first and then rebuild the list to ensure you don't have duplicates in the drop down.