I have a Microsoft Access 2013 application (was previously an .mdb file that I upgraded to .accdb, but it crashed before the conversion anyway so I didn't think this would impact the situation in anyway) with a Report that uses a Query as it's datasource and the Query works perfectly fine.
The Query takes one user parameter input which is a number from 1 to 8. I can use any of those values and the Query works fine and gives the desired results.
The Report uses this Query as it's datasource and works just fine with values 1 and 2, but for input 3, 4, or 5 the Report crashes with the generic and unhelpful message:
This expression is typed incorrectly, or it is too complex to be evaluated. For example, a numeric expression may contain too many complicated elements. Try simplifying the expression by assigning parts of the expression to variables. (Error 3071)
This is a customer application that we inherited (that is, we didn't design or build or code this application) as we do some Access work for other customers.
The customer also gave us a copy of this same application back in January 2015 and the Report works fine for all values. The customer has not changed any forms, reports, queries or VBA code as far as we know (and they are not technically proficient users).
So far, we have spent a couple of days on this and we can't figure out what is causing the report to crash. There doesn't seem to be any tools available in Access to trace this error to which field, data value, expression or anything of that nature that is actually causing the crash. Putting breakpoints in the VBA code shows that the application calls the Report_Open Event, but never gets to the Report_Load event before the crash.
I am looking for an Access guru that may help us to diagnose this.
Is there a way to get Microsoft Partner Hours to help us? I could Zip up the actual Access database and send it to a Microsoft Access expert as the file is only 1.8 MB after being Zipped.
Thank you for your help,
Andre