Crystal Print Engine Error 706

I am trying to add a custom report to the Solomon 6.5 menu
I am getting this crystal error 706
I have searched Knowledge Base with no results
I have followed the directions in article 903102
I can not see the report on the Solomon Menu in AP (Aged AP report)
I also set up the report as a new report format under Aged AP
When I try to execute, I get the 706 error

On Apr 10, 9:35 am, Pboyles <Pboy...@discussions.microsoft.com> wrote:
> I am trying to add a custom report to the Solomon 6.5 menu
> I am getting this crystal error 706
> I have searched Knowledge Base with no results
> I have followed the directions in article 903102
> I can not see the report on the Solomon Menu in AP (Aged AP report)
> I also set up the report as a new report format under Aged AP
> When I try to execute, I get the 706 error
>
> Any help will be appreciated

Can you provide the syntax of the error message please? are you
modifying an existing report or have you created a brand new report

Sorry,
I was not very clear

I wrote the Crystal report 03830.rpt
I tried to put it on the Solomon Menu AP/Reports - It did not appear

I then added the report 03830 to the aged AP report. It did appear on the menu
When I try to execute I get the Crystal Print engine Error 706
I have given myself rights to it as required

"Kambiz Ghassemy - Hitachi Consulting" wrote:

> On Apr 10, 9:35 am, Pboyles <Pboy...@discussions.microsoft.com>
wrote:
> > I am trying to add a custom report to the Solomon 6.5 menu
> > I am getting this crystal error 706
> > I have searched Knowledge Base with no results
> > I have followed the directions in article 903102
> > I can not see the report on the Solomon Menu in AP (Aged AP report)
> > I also set up the report as a new report format under Aged AP
> > When I try to execute, I get the 706 error
> >
> > Any help will be appreciated
> 
> Can you provide the syntax of the error message please? are you
> modifying an existing report or have you created a brand new report
> you are trying to deploy?

By any change are you calling a SL function? Like any RIPARMS? If so,
then you will need to add a preprocess that is looking for those
parameters. It would be good if you could give the whole error.

Thanks.
Jerry

The Aged AP may not be good choice for a report to "clip yours on
to".
It uses a pre-process (stored procedure pb_03680), which, effectively, 
creates where-string data which eventually does get appended to the 
where-clause in the SQL issued by Crystal.
At a quick glance, that proc assumes that the tables/views used by the 
report will include fields RI_ID & cRI_ID.
If the tables/views used by your report don't include those fields, then 
there will be an error of some sort.

I think a basic question is - does your report require a pre-process, and, 
if so, is pb_03680 is a good pre-process to use.

Just a thought or two...

Barry

-- 
Barry Flynn
Complete Solutions DG


"Pboyles" <Pboyles@discussions.microsoft.com> wrote in message 
news:B9138090-C69F-4735-B07E-F07CD778FFAD@microsoft.com...
> Sorry,
> I was not very clear
>
> I wrote the Crystal report 03830.rpt
> I tried to put it on the Solomon Menu AP/Reports - It did not appear
>
> I then added the report 03830 to the aged AP report. It did appear on the 
> menu
> When I try to execute I get the Crystal Print engine Error 706
> I have given myself rights to it as required
>
> "Kambiz Ghassemy - Hitachi Consulting" wrote:
>
>> On Apr 10, 9:35 am, Pboyles <Pboy...@discussions.microsoft.com>
wrote:
>> > I am trying to add a custom report to the Solomon 6.5 menu
>> > I am getting this crystal error 706
>> > I have searched Knowledge Base with no results
>> > I have followed the directions in article 903102
>> > I can not see the report on the Solomon Menu in AP (Aged AP
report)
>> > I also set up the report as a new report format under Aged AP
>> > When I try to execute, I get the 706 error
>> >
>> > Any help will be appreciated
>>
>> Can you provide the syntax of the error message please? are you
>> modifying an existing report or have you created a brand new report
>> you are trying to deploy?
>>