Thanks guys,
I guess I found what it is. What I found on the web was use an IN/OUT parameter which associates to a ref cursor. When it is a IN/OUT parameter, Crystal prmpts for something to input for the ref cursor. I got annoyed with it and made it only an OUT parameter, and it worked like...
I am having trouble with one of my Crystal report which is getting data from a stored procedure thru ref cursor.
When a odbc driver(pdsodbc.dll) is used, the report worked fine on my desktp. When I put it on Crysyal enterprise it gives me dll error.
Some one suggested me instead of odbc...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.