I am using Microsoft Access 2003. I am trying to set up a table in the
design view with a Lookup Wizard Field. I select Lookup Wizard, go
through
all the steps, and then after I click finish, I get the following error
message:
"An error occurred in the Field Builder.
You've replaced or modified the default Field Builder, and Microsoft
Office
Access is unable to run the new version. Reinstall Microsoft Office
Access
to correct the error."
I've reinstalled Microsoft Office, and I'm still getting the error. What
should I do?
Thanks,
Sam Mussmann
Re: How does autofilled form fields info end up in table fields? ... I did use the lookup wizard for these fields and I read the pages you ... I even tried datasheet style form,... > The solution for your report is to include the lookup tables in the query,... (microsoft.public.access.formscoding)
Re: Lookup fields in tables bad? ... My bigger struggles have been with all of the other lookup fields that I ... not sure I understand when a foreign key could be a text box, ...Lists, Field Lists, List Boxes and the like, I’m much clearer now on their ... In table design, if you choose a field of type "Lookup Wizard", you fire up ... (microsoft.public.access.tablesdbdesign)
Re: Lookup fields in tables bad? ... In table design, if you choose a field of type "Lookup Wizard", you fire up ... The Evils of Lookup Fields in Tables ... You also raise the possibility of using value lists rather than a lookup ... fields were one of the benefits of a relational database?... (microsoft.public.access.tablesdbdesign)
Re: Lookup fields in tables bad? ... In table design, if you choose a field of type "Lookup Wizard", you fire up a wizard that many of us don't like. ... That's confusing for developers and newbies alike: you actually have to open the table in design view in order to build a WHERE clause on the field, because you don't know what delimiters you need just by looking at the data. ... You also raise the possibility of using value lists rather than a lookup table. ... (microsoft.public.access.tablesdbdesign)
Re: double database inrelationships? ... >> because you've used Microsoft's obnoxious Lookup Wizard misfeature.... column but the department name would be the visible column.... The relationships window will *still* be flaky. ... (microsoft.public.access.tablesdbdesign)