E
Erica
I posted this in the "Forms" forum, but with no reply. So
maybe it has to do with installation? Here's the problem!
I have recently upgraded to Office 03 from Office 2000.
We're testing out databases and I've noticed this rather
big problem:
I have a combo box that looks up a value from a predefined
table and has a connected filter to it on the form.
The combo box displays the table's bound column, but when
I try to select the item in the list, Access crashes.
In design view, the background error checking reports the
error as "No Such Field in List".
The only thing I could find in the knowledge base had to
do with Auto Expand and SELECT DISTINCT in the SQL
statement. I changed these items, but the error is still
occurring.
I've tested this error on 4 separate computers (3 with
Win2K and 1 with WinXP), all resulting in Access crashing.
One last peculiarity: In a "backup copy" of my database,
I deleted the combo box and followed the Office 2003
wizard to reinstall the combo box with the same SQL
statement. This seemed to take care of the problem.
However, I have DOZENS of combo boxes - there MUST be a
better solution!
You help is very much appreciated -
E.
maybe it has to do with installation? Here's the problem!
I have recently upgraded to Office 03 from Office 2000.
We're testing out databases and I've noticed this rather
big problem:
I have a combo box that looks up a value from a predefined
table and has a connected filter to it on the form.
The combo box displays the table's bound column, but when
I try to select the item in the list, Access crashes.
In design view, the background error checking reports the
error as "No Such Field in List".
The only thing I could find in the knowledge base had to
do with Auto Expand and SELECT DISTINCT in the SQL
statement. I changed these items, but the error is still
occurring.
I've tested this error on 4 separate computers (3 with
Win2K and 1 with WinXP), all resulting in Access crashing.
One last peculiarity: In a "backup copy" of my database,
I deleted the combo box and followed the Office 2003
wizard to reinstall the combo box with the same SQL
statement. This seemed to take care of the problem.
However, I have DOZENS of combo boxes - there MUST be a
better solution!
You help is very much appreciated -
E.