quote:Originally posted by mossimo
I got it to work but I will admit I have herd this rumor before do you know what the story is? Possibly slower performance or poor data structure.
It has to do with data integrity and structure. If you're the only person working on this database and table then it's perfectly all right to do it this way. You're the only person dealing with the data.
However, the instant you share this with other people, it becomes a poor practice because users should never edit data directly in a table. They should use a form. Dropdowns and the like are created and structured in the form. The table's purpose is just to hold the data... period. Therefore, you don't put dropdown elements in your table.
I can see the allure of making dropdowns in tables because whenever you create a form based on this table and bring in that field, it will automatically turn into a dropdown with the proper rowsource. However, some folks say it's even bad structure to base a form on a table or query and that you should always use unbound forms. It's all a matter of standard practices and uses.
Michigan Dept. of Environmental Quality, Air Quality Division