You can do the table export via a query; however, it sounds like there's more to this than "first meets the eye."
Lets' see if we can make this better... sounds like you need a bound ComboBox control here - for short CBO.
Wherein Lookup fields at the table level are frowned upon almost universially, in a normalized database, we need the equivalent at the form level (and often at the query level)... and the CBO is our friend!
CBO have two properties:
Control Source
Row Source
- In a bound form the Control Source would be bound to one of the recordset's fields
- The Row Source can be a list (for simple stuff), a query (either stored or embeded), or a table.
I have a form that shows an example of this here:
http://bytes.com/attachments/attachm...ead_943879.zip
KEEP IN MIND! That this DB was made in answer to BytesThread943879. It is only provided here so that you can see what I am talking about for the BOUND-CBO used in the form.
If you open the database, place the main form (it should open when you open the database)
in design view.
In the
details section, you'll see the CBO that are
bound to the underlying recordset of the form.
Right click on the first CBO(actually any)
in the details section and show the properties. Each CBO has an Embeded Select Query, You could just as easily taken the query and saved it as one of the stored queries and referenced the stored query or indeed one of the tables.
These provide a nice human readable text while setting the numeric value of the primary key from the related table.
So you should be able to do the same thing with your database.
Feel free to look at the remaining stuff in this database; however, most of it will not apply to your question.