I am having a problem with a crosstab query that results in no data,
which is fine, but the report generates an error. I read here that you
can add ColumnHeadings to the query properties, which also work.
However, in my report I tried using for row source
=Iif(iserror([60-90],null,[60-90]). Now, if there is an error
generated, it provides null as the value. However, if the field is not
an error it still nulls out the value. I would like to not see a page
of #Errors, but I would also like to have my information be correct.
What is wrong with this?

If you only see this #Error on the report when the crosstab returns no
records at all, you could avoid it by testing the NoData property of the
report:
=IIf([Report].[HasData], [60-90], Null)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I am having a problem with a crosstab query that results in no data,
> which is fine, but the report generates an error. I read here that you
> can add ColumnHeadings to the query properties, which also work.
> However, in my report I tried using for row source
> =Iif(iserror([60-90],null,[60-90]). Now, if there is an error
> generated, it provides null as the value. However, if the field is not
> an error it still nulls out the value. I would like to not see a page
> of #Errors, but I would also like to have my information be correct.
> What is wrong with this?

OK, with that now I get an #Error.

I typed that into the textbox ControlSource verbatim.


Allen Browne wrote:
> If you only see this #Error on the report when the crosstab returns no
> records at all, you could avoid it by testing the NoData property of the
> report:
> =IIf([Report].[HasData], [60-90], Null)
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >I am having a problem with a crosstab query that results in no data,
> > which is fine, but the report generates an error. I read here that you
> > can add ColumnHeadings to the query properties, which also work.
> > However, in my report I tried using for row source
> > =Iif(iserror([60-90],null,[60-90]). Now, if there is an error
> > generated, it provides null as the value. However, if the field is not
> > an error it still nulls out the value. I would like to not see a page
> > of #Errors, but I would also like to have my information be correct.
> > What is wrong with this?

I fixed it. I had to change the name of the TextBox to txt60_90 for it
to work. Thanks!


(E-Mail Removed) wrote:
> OK, with that now I get an #Error.
>
> I typed that into the textbox ControlSource verbatim.
>
>
> Allen Browne wrote:
> > If you only see this #Error on the report when the crosstab returns no
> > records at all, you could avoid it by testing the NoData property of the
> > report:
> > =IIf([Report].[HasData], [60-90], Null)
> >
> > --
> > Allen Browne - Microsoft MVP. Perth, Western Australia
> > Tips for Access users - http://allenbrowne.com/tips.html
> > Reply to group, rather than allenbrowne at mvps dot org.
> >
> > <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > >I am having a problem with a crosstab query that results in no data,
> > > which is fine, but the report generates an error. I read here that you
> > > can add ColumnHeadings to the query properties, which also work.
> > > However, in my report I tried using for row source
> > > =Iif(iserror([60-90],null,[60-90]). Now, if there is an error
> > > generated, it provides null as the value. However, if the field is not
> > > an error it still nulls out the value. I would like to not see a page
> > > of #Errors, but I would also like to have my information be correct.
> > > What is wrong with this?