OKay, I have an update...

The report I am calling, includes a subreport.
If I change the reporttag to call the sub-report alone, then the
report runs correctly as requested.

I have removed all sub-reports and now only have one (sub report).
And I still ge the error message.

So it would seem there is an issue with the reportparam being used by
a subreport.
It doesn't help me any in solving it.... but it might help smeone else
who has done this already and worked it out.

Thanks agan.

On Jul 9, 1:53 pm, Gavin Baumanis <beauecli...@gmail.com> wrote:
> Hi Everyone,
> I am back to trying to fix my reporting issues and have been working
> on it for the past three hours - and I have finally thrown the towell
> in!
>
> I am creating a structure, that stores the results of several queries.
> if I dump the structure, (from the page that contains the cfreport
> tag) I get  an appropriate dump of a struct with the expected key-
> value pairs.
>
> I then use the struct as a reportparam.
>
> <cfreport
>         template="print_CAR.cfr"
>         format="pdf">
>                 <cfreportparam name="reportParamStruct" 
> value="#reportParamStruct#">
> </cfreport>
>
> But I get the following error when I try and run this page;
> Error evaluating expression : Source text :
> param.reportParamStruct.problemdescription
>
> I have tried with and without pound signs, I have also included a
> "print when" condition that checks for the structure and its key
> exisiting and that the key isn't an empty string.
>
> seemingly no matter what I try - I still get the above error.
>
> If anyone has any ideas at all - I would be most grateful.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to 
cfaussie+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to