Report Center & Crystal Report subreports

[Gapman]

Hi All -
This is my first post. I am writing my first set of Crystal Reports for Report Center. Most worked OK, but for those that contained sub-reports, I got multiple parameter fields and the following error boxes:
"656-Error in File C:\.....rpt; Operation illegal on linked parameter.:StartDate" (note: StartDate is on of the input parameters)
"656-Error in File C:\.....rpt; Operation illegal on linked parameter"

Any assistance would be greatly appreciated.

Thanks,
- Kent

[danstenzel]

Hi Kent -
Don't know if this will help, but Peregrine Knowledge Search Document Id 78445 has a description of:
"Cannot run Crystal Reports or ReportCenter reports against ServiceCenter data if the selection query uses dates ranges as the selection criteria."

The Cause is:
"The box labeled 'Uses Indexes Or Server For Speed' is selected (checked) by default. As a result, Crystal Reports is looking for items that are indexed, but dates are not indexed."

The Resolution is:
"From the File menu, click 'Report Options'; Clear the check box labeled 'Use Indexes Or Server For Speed'."

I found another check box of the same name here:
File->Options->Database Tab->Advanced Options section.

Hope this works for you.

Dan

[danstenzel]

I was working on a monthly close report, and found another possible solution. Crystal Reports decides internally which criteria (i.e. "Record Selection Formula") to pass along in the SQL and which criteria it will handle in filters. Any field used in a "true" formula will be "filtered" instead of put in the SQL. Here's what I did:

and ({probsummarym1.close.time}+0.000001) > {?StartDate}
and ({probsummarym1.close.time}-1) < {?EndDate}

I used discrete value data parameters, and then manipulated the database fields to make them be inclusive (as if I had entered a date range).

As an aside, I looked at the SC we are running (6.0.1.0) and it appears that it DOES have indexes built on the dates - but they are DTS (? not exactly sure what that means ?) and when the SQL is built - it builds the date/time it is preceeded by "TS".

Anyway - forcing the date field into a formula (and therefore into the filter) worked for me, and I didn't have to worry about how the ODBC driver would handle the SQL / GMT conversion.

[daurkin]

I know this is such an old article, but thanks because this helped out my report. It runs slower, but at least it runs.

I don't supose you were able to get Report Center to "not prompt for those Parameters in the subreport" when they are properly linked to parameters in the main report?

[danstenzel]

Sorry, can't help you there, I haven't played with using subreports.