I have a report parameter that is type string and the related stored procedure has its parameter as varchar(x). The reason the parameter is set up as a string is because the VB app that renders the report dynamically sets up some pre-determined default report parameters and has declared them as strings (I can't change the VB program). In this particular case, the report is expecting a year(YYYY) parameter and it runs fine in SQL Query Analyzer. When I add the SP to the report and execute, I get the parameter input box, but when I input a year, Crystal abends with CR32.exe error and completely shuts down.
Has anyone seen this behavior? I am using V8.5.
Rene'
Has anyone seen this behavior? I am using V8.5.
Rene'