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!

Entering incorrect parameter.gives datatype String (128)

Status
Not open for further replies.

rineen

Programmer
Aug 10, 2005
4
GB
I am using CR10 connecting to an Oracle database and using a stored procedure to bring back the data. I don't have access to the Stored procedure or database as this is created and maintained by another department. When I run the report if an incorrect parameter is entered I get the map fields screen. If I map the fields it is displaying I find that all the fields brought back by the SP are changed to datatype string (128). What should be happening is that an error field returned by the SP should display the details of the incorrect value entered. This is how it works on other reports. If I add the fields to a new blank report I don't get the problem. Since the report was first created both it and the SP have been changed as the requirements have changed. The report is quite complex so want to avoid redoing it from scratch. Anyone come across this happening before and know of any solutions.
 
Hi,
Have you done the 'verify database' step on this report?
Every time the SP changes you need to do that..



[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Hi Turkbear,
Thanks for your reply
Yes I have verified the report and everything is returned correctly. This problem is only occurring if an incorrect parameter value is entered when running the report. The SP has some error handling to check the values entered and if these are incorrect writes an error message to a field which I have put on the report. This works on other reports using similar stored procedures but not on this one. I have created a new test report to try and recreate the problem using the same Stored procedure as the problem report and it works fine so I don't think it is a problem with the stored procedure. Whilst it would probadly be quicker to redo the report my main concern is if the user wants some more changes to the Crystal Report and/or the stored procedure then this problem could happen again at a later date.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top