Report works for some dates not others

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bob - 26 Oct 2005 20:50 GMT

I have a cross tab report that has two parameters startdate and enddate. It
runs fine from 4/1/05 to 6/30/05 and from 4/1/05 to 9/30/05 but I get a Run
Time 3070 error if I run it from 7/1/05 to 9/30/05.

All the expression fields in the report use NZ([xxx]) to prevent nulls from
messing up the results. Any ideas would be greatly appreciated.

Reply to this Message

Dennis - 27 Oct 2005 10:50 GMT

I think I had this problem a few years ago but am not totally sure. Mine was
because the data that the query returned between certain dates was different
to other dates in that it did not create the same column headings in the
cross tab.
My report was directly accessing the name of one of these headings and it
exists in one date range but not the other and so the error.

> I have a cross tab report that has two parameters startdate and enddate. It
> runs fine from 4/1/05 to 6/30/05 and from 4/1/05 to 9/30/05 but I get a Run
> Time 3070 error if I run it from 7/1/05 to 9/30/05.
>
> All the expression fields in the report use NZ([xxx]) to prevent nulls from
> messing up the results. Any ideas would be greatly appreciated.

Reply to this Message

Duane Hookom - 27 Oct 2005 14:20 GMT

I expect this is a data error. Try narrow the date range down to see if you
can find the specific date/record that cause the problem. Then review the
data records for that date.

Signature

Duane Hookom
MS Access MVP

>I have a cross tab report that has two parameters startdate and enddate.
>It
[quoted text clipped - 5 lines]
> from
> messing up the results. Any ideas would be greatly appreciated.

Reply to this Message

Bob - 27 Oct 2005 15:50 GMT

Thanks for the help. It was a data problem. It turns out that in the
quarter there was not a single entry for one one of the fields, so the column
didn't exist in the cross tab queary the report was based on. So now I have
a new question. Is there a way to keep this from happening without creating
place holder data each quarter? Thanks.

> I expect this is a data error. Try narrow the date range down to see if you
> can find the specific date/record that cause the problem. Then review the
[quoted text clipped - 9 lines]
> > from
> > messing up the results. Any ideas would be greatly appreciated.

Reply to this Message

Duane Hookom - 28 Oct 2005 04:05 GMT

It would help to see your SQL view. You can usually set the Column Headings
property of the crosstab to specify all possible columns.

Signature

Duane Hookom
MS Access MVP

> Thanks for the help. It was a data problem. It turns out that in the
> quarter there was not a single entry for one one of the fields, so the
[quoted text clipped - 19 lines]
>> > from
>> > messing up the results. Any ideas would be greatly appreciated.

Reply to this Message