Union query parameter is too complex error 3071

  • Thread starter Thread starter dreamsoul620 via AccessMonster.com
  • Start date Start date
D

dreamsoul620 via AccessMonster.com

Hi all,

I have two reports that I want to run based on a selection the user makes in
a combo box. I have two buttons on my form as well. The first button runs a
basic query that uses the combo box selection as the parameter for my query.
The second button runs a union query, which works fine if there is no data
for the selected user. For example, Employee A had a dress code violation
and Employee B has not had any violations, the query would run for B but give
an error for A stating that the expression is typed incorrectly or is too
complex. The queries ran fine when I had the query give the user a prompt to
type the parameter (or employee).
The first query pulls current violations. The union query pulls current
violations (current table) and old violations (history table). Please help!!!
I cannot seem to find anyone that has solved this issue.

Thanks.
 
Can you post the SQL of the two queries? It would also help if you gave us
some informtion about the table structure of the table(s) being used.

Dale
 
In researching, I found this is a common error with access. Using union
queries with multiple parameters throws an error everytime. Thanks for help
though.

Dale said:
Can you post the SQL of the two queries? It would also help if you gave us
some informtion about the table structure of the table(s) being used.

Dale
[quoted text clipped - 12 lines]
 
Back
Top