- Local time
- Today, 13:19
- Joined
- Feb 19, 2002
- Messages
- 45,726
There is nothing different about how they behave. The bound column is still the ID. the issue is that most people don't understand that. They open the table or a query and they see the text. Therefore, they assume, incorrectly, that they are working with a string rather than the ID. So they add to the confusion by naming the FK with the name of the text field rather than the ID ensuring that they never know what they are working with. So they create queries that search on the text string but of course, the table holds the ID so nothing is found. They write code that works with a string but the field is actually an ID. That is just the tip of the iceberg. Over time, MS has actually fixed some of the issues but that made them not work for people who knew what they were doing.Hi Pat. I have never been able to get table lookups to work for me very well, so I never use them, but I have a question. If you do add a table lookup field to a form as suggested above, do you still get the same Event Procedure options such as Before Update and After Update as you do by adding a combobox to a form?
Last edited: