The problem you have is that you don't send field data to a combo box. You
send a "field", or what is refereed to is a column.
So, listbox, or a combo box needs to you give it what field to display, and
you can also have some criteria for that combo box.
select City from tblCites where Country = 'Canada'
The above sql thus could fill the combo box with all cities from my country,
assuming we have nice database off all Countries. Note have we have a table
with the data, we do NOT have a database with:
City_USA City_Canada City_Germany
Note how the above is a real mess from a data design point of view. You
should NEVER have multiple fields in a record to store repeating data. So,
for example, the above record that holds cites as above would be converted
to:
City Country
Edmonton Canada
New York USA
Calgary Canada
Further, for making reports and filling combo boxes, you can see how ease
the last example is to work with. Further, if I have to add a new city to
the database, then I NEVER have to add a new field. Adding fields is really
hard, since all forms, reports, combo boxes etc will have to re-built or
modified if you add a new field. So, your designs should be such that new
data should NOT take a new field. This whole process of data modeling is
called normalization.
In your case you have:
a1_1, a1_2, a1_3, etc.
Those values should be broken out to another table, and then *RELATED* back
to the current record. That way, you can have as many, or as few values for
the one record you want (this is called a one to many relationship).
It is also not clear if you need to fill the combo box with values a1_1,
a1_2, a1_3, etc from ONE record, or all records together? Doing this is a
bit messy. You don't mention how many values you have in that record.
(a1_?).
If the combo is to be filled with data form just ONE record, then you can
write a loop to build a source for the combo box (but, what are you gong to
do with the combo box then?).