VB.NET 2005 & CR w/ Parameters

I've searched here and MSDN, and CR website, and all over.... and I can't seem to find a solution to my problem, and it's getting to the do or die point in the project.

Here's the deal, I'm doing this on a shoestring budget.... in fact it's only one shoestring, not enough capital to get the other shoestring. I need to have the ability to supply reports to a client, so I figured I'd use the CR that came with VS2005. It's not bad, but it will suffice for my needs. The problem though are the parameters. I can't seem to get it to work. I did find a few tutorials on how to set them, and when it comes to setting them I don't have a problem.... Until I deploy to the client.... My client is reporting that the app errors out with a "Expected parameter @XYZ was not supplied" Huh? I've had him run the SP through Query Analyzer.... and it works... he gets the data.... but for some reason, it just won't work for the client, but it does for me, so I'm having some issues in troubleshooting this.

Ideas, suggestions hints? It appears to connect OK to the database... but there's no telling what the parameters are doing..... It just occurred to me that we haven't tried a parameter-less report... jsut something to select data and spit it out... will have to try that tonight.

If necessary, I can post the code that shows how I'm connecting to the database, and passing the parameters.



-tg

Did you create an installer and deploy the merge modules for CR?

YEs.... the report works... it's just that it complains that a parameter wasn't sent when it was. CR then trows up it's built-in "Enter Parameter Values" dialoge box, and if entered right, the report renders.... I'm trying to avoid doing that.

I found some code in my snippets area of VS last night, haven't tried it yet, but the code it provides is yet different again from everything else I've tried. I figured at this point it can't hurt.

-tg

I don't use CR that way for one of those reasons, I find it much better to use a disconeected recordset of the data that CR needs in the report and send that to the report. That way you have total control of whats going on and CR is only used to display the results.

That way if a calculation changes, it gets changed in the code and you never have to change the report.

I feel the other way, I do everything in stored procedures, the report is just a store front. If I need to make a change to the calc, I change the SP, and ship it. No need for an install.

-tg

Yes, Code is still code...