Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Crystal Reports 10 - Invalid Argument Error

Status
Not open for further replies.

p8ass8

IS-IT--Management
Jun 18, 2007
13
US
I have a report that takes a USERID value(int) as a parameter(user supplied). This report works for all parameter values except one(so I know this has nothing to do with stored procedure permissions).

If I run the associated stored procedure independently for this parameter value, it returns the complete result set. Also, the data obtained from the database tables is validated, so I doubt that the report encountered some invalid value. The Stored Procedure that the report uses does not call any other procedure.

I don't understand what invalid argument the report comes across causing it to throw this error.

The only thing I can think of is the enormous result set that is returned for this particular parameter(over 8000 records). Is there a limit to the report size in Crystal Reports version 10?
 
No real limit to result set.

It could be a formula in the report which is failing when it gets to 8000+ records.

Check to see if there are any formula using record count in any way. If yes try removing from report and see if it runs.

Are there any arrays which could potentially go over 1000 elements. Again if yes suppress and see what happens.

Ian

Ian
 
Just a random thought here. Are you using any formulas like date of birth where Feb.29 is not accounted for? I've seen reports error out after many records because the report encounters a Feb.29 that has not been accounted for in an age formula.

-LB
 
Thank you for your replies. Eventually turned out that a join was taking too long and perhaps caused Crystal to timeout or something. When I removed the join from Crystal, and did it in the stored procedure instead, the report started to work fine. So now it works! Thanks again
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top