Reporting Services - Parameters
Uploader Comments (PCTeachME)
All Comments (25)
-
Hi,
it was the driver. It is kind of funny thou. For testing purposes i tried to connect via odbc and with odbc bids 2008 can't work with bind variables - at least from my experience.
After i connected via tns it works ok with binds.
Anyways - my problem now is importing the 2005 rdl's in 2008. Import project does not work. Do you know of any program that does the rdl conversion from 2005 to 2008 (i don't have time to edit the "xml" version by hand)
thanks
Titus
-
Hy,
I have a little question maybe you can help me.
I use bids 2008 (i worked on 2005 with no problems) with oracle database.
In 2005 i used to do the dataset parameters using ":parameter". In 2008 it does not recognize this type of parameter and @ is not recognizes either.
Do you have any idea which is the new format for oracle parameters?
thanks
-
Great Video! Thanks.
-
Thanks, great video. You've given me some good ideas.
-
Excellent explanation...Thanks...
@titusm hi, great news about driver. Welcome to my world regarding conversion ! You can deploy 2005 reports to a 2008 box i believe. But as the so called visual studio "wizard" goes I have not come across any other way other than xml alteration or recreation in 2008 (not to say there isnt a way but I dont know of one). To ease deployment pains have you downloaded "Bids Helper"?
PCTeachME 1 month ago
Hy,
I have a little question maybe you can help me.
I use bids 2008 (i worked on 2005 with no problems) with oracle database.
In 2005 i used to do the dataset parameters using ":parameter". In 2008 it does not recognize this type of parameter and @ is not recognizes either.
Do you have any idea which is the new format for oracle parameters?
thanks
titusm 1 month ago
@titusm Hi, That is odd! It sound definatley something with the driver (if the same code worked in the past). Is there a conflict with the Oracle TMS driver (I hate those things!)? Can 2008 report work without parameters? Sorry you may have done all these things already but need to start somewhere... If you happen to already worked out the answer please update on here for any other users :)
PCTeachME 1 month ago
Wow why is it so painfull to get a date parm to work with DB2 (odbc). I have a simple query that runs fine (just testing), and have put in a startdate parm, added the @startdate in the SQL, and it continually gets the "-206 @startdate is not valid in the context where it is used". I have it entered under dataset properties and under the parameter entry, it looks like everything is in place but still get the error everytime. Is something else needed with DB2?
jflor98 6 months ago
@jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.
PCTeachME 6 months ago
GIVES ME ERROR ON WHERE CLAUSE FOR @
TheZaakhan 7 months ago
@TheZaakhan Hi, If you go to my web site PCTeach [dot] me. Look at the contact menu and my email is there. Send me a zip of your work so I can work out specifically the issue. From the error sounds like you are trying to put a value on a parameter (or asssigning the parameter) to a value which does not accept booleans (TRUE/FALSE values). Sometimes, putting the word "true" or "false" does not work, try "1" for true or "0" for false. IF still no joy email as stated above. Thanks.
PCTeachME 7 months ago