Unfortunately it's exactly what's happening. The description of the parameter is what is being passed because that is what is showing in ePortfolio. The parameter itself is a Crystal only parameter which gets it's default values set inside the Crystal report. So for example when a user...
This is using Crystal Enterprise 9.
I have a parameter field that has for it's values 4 different numbers each with their own description. When a user chooses to schedule the report in ePortfolio and they choose the option they want for that parameter field and hit add it puts the description...
Thanks for the help. Your comments put me on a different track so now I've chosen a completely different method that doesn't use the dynamic sql and doesn't give me an error message.
I'm using sp_executesql because the ID field is a security field which could include several different numbers 1,2,3,4,5 for example so the client only sees information specific to them. The only way I know of to be able to send that range in as a parameter, is to do it the way I am currently...
I have a Crystal report with one subreport. The main report and the subreport are linked to the same stored proc. The stored proc is basically the following at the end.
When I link the parameter fields from the main report to the subreport (so the user doesn't have to fill them in twice), I...
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.