too complex to be evaluated?

[Guest]

I have a report in my database that has been working perfectly for months.
No changes have been made to the report or the queries it is based on. Today
when I try to run the report, I get a "too complex to be evaluated" error.
The SQL of the query behind the report is

SELECT [Q_Past Due Banking Curtailments Part 1].[Dealer Name], [Q_Past Due
Banking Curtailments Part 1].[Serial#], [Q_Past Due Banking Curtailments Part
1].Manufacturer, [Q_Past Due Banking Curtailments Part 1].Model, [Q_Past Due
Banking Curtailments Part 1].Year, [Q_Past Due Banking Curtailments Part
1].[Line Type], [Q_Past Due Banking Curtailments Part 1].LineCat, [Q_Past Due
Banking Curtailments Part 1].[Maturity Date], [Q_Past Due Banking
Curtailments Part 1].[Floored Date], [Q_Past Due Banking Curtailments Part
1].[Original $ Floored], [Q_Past Due Banking Curtailments Part 1].Expr,
[Q_Past Due Banking Curtailments Part 1].expr1, [Q_Past Due Banking
Curtailments Part 1].expr3, [Q_Past Due Banking Curtailments Part
1].DueinFull, [Q_Past Due Banking Curtailments Part 1].FlooredDtDaysPastDue,
[Q_Past Due Banking Curtailments Part 1].Outstanding, [Q_Past Due Banking
Curtailments Part 1].Curtailment, [Q_Past Due Banking Curtailments Part
1].MatMonthsPastDue, [Q_Past Due Banking Curtailments Part 1].OnReport,
[Q_Past Due Banking Curtailments Part 1].MonthsOnBooks, [Q_Past Due Banking
Curtailments Part 1].DaysOnBooks, [Q_Past Due Banking Curtailments Part
1].CurtDate
FROM [Q_Past Due Banking Curtailments Part 1]
WHERE ((([Q_Past Due Banking Curtailments Part 1].OnReport) Like "Yes"));

As you can see, all of the values are coming from Q_Past Due Banking
Curtailments Part 1, which opens and displays results without error. The
only function of the "Part 2" query is to determine whether the expression
"OnReport" has a value of "Yes" or "No" in the Part 1 query.

I have two other, almost identical reports (same criteria except pulling for
specific dealerships) that also use the Part 1, Part 2 structure with the
"OnReport" field that still work correctly.

Any suggestions?

 

[Neil Sunderland]

I have a report in my database that has been working perfectly for months.
No changes have been made to the report or the queries it is based on. Today
when I try to run the report, I get a "too complex to be evaluated" error.
The SQL of the query behind the report is [snipped]
As you can see, all of the values are coming from Q_Past Due Banking
Curtailments Part 1, which opens and displays results without error. The
only function of the "Part 2" query is to determine whether the expression
"OnReport" has a value of "Yes" or "No" in the Part 1 query.

I have two other, almost identical reports (same criteria except pulling for
specific dealerships) that also use the Part 1, Part 2 structure with the
"OnReport" field that still work correctly.

Any suggestions?

It could be a couple of thinks: does it need to be 'Like "Yes"' in the
WHERE clause? Have you tried '= "Yes" instead?

Occasionally, the length of the query can cause problems, which you
can fix by using an alias. Try this:

SELECT Q.[Dealer Name], Q.[Serial#], Q.Manufacturer, Q.Model, Q.Year,
Q.[Line Type], Q.LineCat, Q.[Maturity Date], Q.[Floored Date],
Q.[Original $ Floored], Q.Expr, Q.expr1, Q.expr3, Q.DueinFull,
Q.FlooredDtDaysPastDue, Q.Outstanding, Q.Curtailment,
Q.MatMonthsPastDue, Q.OnReport, Q.MonthsOnBooks, Q.DaysOnBooks,
Q.CurtDate
FROM [Q_Past Due Banking Curtailments Part 1] AS Q
WHERE Q.OnReport = "Yes";

Since it's all coming from a single table/query you can omit the
source from all the field names, but it's best to use an alias
otherwise Access might put the full table/query names back in if you
edit the query later!

 

[Guest]

Normally that error occcurs when you don't explicitly type a date parameter.
I see the query uses dates - maybe check for that?

HTH