wlrthjoilihjw
Programmer
hi, all.
I use the CrystalReportViewr component in my VB.NET WebApplication to show reports created in CR9/CR10. Reports run against a SQL 200 DB using a stored procedure as a datasource.
In my reports I've renamed the stored proc parameters, e.g. @employee_id into Employee.
In my VB.NET code I use ApplyLogonInfo to set the new datasource information, because the name of production database differs from the name of the DB used to create reports. I've used the sample code from the Business Objects site.
After applying new logon information my parameter names seem to be OK: debugging through the ParameterFields collection I still see the "Employee" as parameter name. After that the report parameter prompt is displayed on the web page, and there's "@employee_id" instead of my human readable param name. After submitting of all necessary parameter values, the report crashes (.NET error message is displayed: "System.ArgumentException: Wrong Parameter" or so).
But it all works perfectly if I use the database with the same name as the report development DB has.
I never had such a problem with my old VB6 stand alone applications using RDC 9... I hope, there would be anyone knowing some approaches to solve the issue, otherwise I'll be probably placed in a mental health facility for crystal reports victims...
TIA
I use the CrystalReportViewr component in my VB.NET WebApplication to show reports created in CR9/CR10. Reports run against a SQL 200 DB using a stored procedure as a datasource.
In my reports I've renamed the stored proc parameters, e.g. @employee_id into Employee.
In my VB.NET code I use ApplyLogonInfo to set the new datasource information, because the name of production database differs from the name of the DB used to create reports. I've used the sample code from the Business Objects site.
After applying new logon information my parameter names seem to be OK: debugging through the ParameterFields collection I still see the "Employee" as parameter name. After that the report parameter prompt is displayed on the web page, and there's "@employee_id" instead of my human readable param name. After submitting of all necessary parameter values, the report crashes (.NET error message is displayed: "System.ArgumentException: Wrong Parameter" or so).
But it all works perfectly if I use the database with the same name as the report development DB has.
I never had such a problem with my old VB6 stand alone applications using RDC 9... I hope, there would be anyone knowing some approaches to solve the issue, otherwise I'll be probably placed in a mental health facility for crystal reports victims...
TIA