Failure to retrieve data from the database (Vendor Code 6550)

[#1]

I am having a trouble with two of the 6 reports that I have created. I am using Crystal XI and Oracle 10g. The underlying database object is a stored procedure that accepts as input a start time as a TIMESTAMP, an end time as a TIMESTAMP and a furnace number as a number. I have a cursor ref as a return parameter.

When I run the stored procedure in Oracle I get the selected records and can view them on the screen.

When I refresh data on the report in Crystal XI developer, the designer asks me for the start and end time and furnace number. When I input these values the report displays properly.

When I launch the report from my VB .NET 2005 application I am asked for the username and the password for the database (this is another problem I need to solve as this information I put into the program seems to be ignored in my program) then I receive the following failure message:

Failure to retrieve data from the database (Vendor Code 6550)

When I launch the other reports, they only ask me for the username and password then they display the proper data.

The main difference between my other reports and the two that are returning the above failure code is that the other reports are to either tables or views. The two that don't work are tied to stored procedures. I there any way that I can solve this problem or at least get more information?

Any help would be greatly appreciated. Let me know if you need any other information.

[Former Member]

Dear Don,

My .NET web page vendor have replied to me stating that the Code is not the issue, he tried to insert a simple one query sub report to my preexisting main report, and it is able to load with no issues. This is what hey have done.

1) Create a new sub report link to the main report

2) He later added a connection to the database and executed a simple command to
retrieve some data.

3) He deploy the new main report to the .NET web application and got the screen below:-

4) He then tested the newly created sub report to see if it could load and it loaded successfully

What he further suggested is that I do something similar, by adding a simple sub-report to my existing report to make sure that it works and then gradually add complexity to my report (i.e. pass parameters to it, call stored procedures etc) and build up the sub-report that I require.  It is possible at some point I will encounter the error that I am getting now, but as I have gradually built the report I will know what it is that I have added that has caused the problem.

Any other better suggestions?