|
||||||
|
Lookup Wizard By Richard Rost 10 months ago Avoid Lookup Wizard & Fields in Access Tables In this Microsoft Access tutorial, I will show you how to correctly replace Lookup Wizard fields with a more efficient method, ensuring changes to your product codes only need to be made in one place. Cameron from Chapel Hill, North Carolina (a Platinum Member) asks: I started building my database before I found your tutorials. I know that you don't like the Lookup Wizard, but I have lookup fields in a lot of my tables, and now I need to get rid of them. I can see why you don't like them. One of the lookup tables that I have is for product codes, and instead of making a separate table for that, I used the lookup field that I copied into four different tables. Now, every time I need to change one of those product codes, either add or delete one, I have to do it in four different places. Are there any tips you can give me for how to set this up properly, and how to easily take my list of a few hundred product codes and put that into a table properly? PrerequisitesLinks
Recommended Courses
KeywordsTechHelp Access, Lookup Wizard replacement, efficient product codes, avoid Lookup Wizard, relational database setup, fix multiple table updates, normalization in Access, manage product code changes, Access design view, update queries in Access, avoiding multi-value fields, SQL Server transition, proper Access table setup, relational database principles, junction table in Access
|
||||||||||||||||
| |||
Keywords: TechHelp Access, Lookup Wizard replacement, efficient product codes, avoid Lookup Wizard, relational database setup, fix multiple table updates, normalization in Access, manage product code changes, Access design view, update queries in Access, avoiding m PermaLink Lookup Wizard in Microsoft Access |