J
Jerry McManus
My main form is based on a query based on a back end .mdb. I use local
front end lookup tables with comboboxes to display the descriptions for
coded fields. Record source for the combos is SQl, such as "SELECT [ztlkTax
Rider].Code, [ztlkTax Rider].Description FROM [ztlkTax Rider] ORDER BY
[ztlkTax Rider].Description; "
It works fine on the form, but when I run a report based on the filtered
form I get the following error message "Lookup_TAX__RIDER.Description."
The query for the main form includes the coded single character ID for the
the field rather than the description.
Looking at the filter that is sent to the report the following has been
inserted "((Lookup_TAX__RIDER.Description="Percentage"))
Although the main form interprets this "Lookup_" the report cannot.
Question: Is there a workaround or setting to allow the use of the combobox
lookups from code or do I have to set my query to do the lookup first for
the main form, which would entail much greater network traffic?
front end lookup tables with comboboxes to display the descriptions for
coded fields. Record source for the combos is SQl, such as "SELECT [ztlkTax
Rider].Code, [ztlkTax Rider].Description FROM [ztlkTax Rider] ORDER BY
[ztlkTax Rider].Description; "
It works fine on the form, but when I run a report based on the filtered
form I get the following error message "Lookup_TAX__RIDER.Description."
The query for the main form includes the coded single character ID for the
the field rather than the description.
Looking at the filter that is sent to the report the following has been
inserted "((Lookup_TAX__RIDER.Description="Percentage"))
Although the main form interprets this "Lookup_" the report cannot.
Question: Is there a workaround or setting to allow the use of the combobox
lookups from code or do I have to set my query to do the lookup first for
the main form, which would entail much greater network traffic?