Wizard Dropdown menus don't update records

I have a multiple table database with several tables being used almost exclusively for drop down menu input (to minimize user spelling/typo issues).

When I create the dropdown menu's in DataAssist Wizard, they create perfectly, look great, and are completely useless.

I followed the Data Assist tutorial (which I can't find again ... GDI!!) where I learned how to make the menu dropdowns, and they worked great the first time I did it, but then I realized, I wanted the "name" not the "id" to show in the results and details pages.

I re-ran the wizard (about 12 times now) and I can't get menu drop downs to display only the name, sort by the name, etc...doing NOTHING with the ID.

I tried to add an INNER JOIN to the query at one point, and that didn't work either, although, given there is no associative table between the 2 tables, I don't think that is necessary...

Thoughts? Help? Bandage for my head or repair kit for my desk?

Ken

with a dropdown (list/menu), there are 2 elements, value and label.

the 'value' is stored/retrieved from the DB, the 'label' is displayed on the screen.

if you need more help, zip and attach the page in question.

I understand how the 'name' and 'id' fields relate, the problem I am having it is always saves a "0" regardless of what I select from the dropdown....

I have attached a zip with all of the files created by the DataAssist Wizard in this example, in case anything on the other pages is relevant, however, the issue is on the Insert and Update pages.

Thanks for looking into this.

Ken

Not sure if this is the reason why you are getting the problem, but i think the problem is that your dropdowns contain the name for both the id and the value in each case.
You say you are getting a '0' inserted, which means the database is expecting an integer.
you should really be storing the id for the value, which should be an integer from your table, - not a text variable.

i also noticed in your select statements, you are repeating the name field for each dropdown recordset, is there a reason for this ?

does this make sense ?

if not, please send a copy of your table structure and i can advise further

That does make sense!!

I was always intending to use the ID as the FK - but when i started having issues, I switched to names...which don't store...

I will try changing to the ID field stored...

Thanks!!

Ken