Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Web Error/Bug Help

Status
Not open for further replies.

excalibur78

IS-IT--Management
Jan 3, 2001
66
US
Not sure if anyone has run into this error/bug yet but I couldn't find anything on it. I have a working report with numerious parameters running on CR8.5 via IIS5. Reports run fine except when you click the Add button without selecting anything in a parameter and it added a "" to the multiple select parameter. I get an error but when I add a "" in the designer to test locally I can't get this error. Only happens via the web when run. Any ideas would be great.


David
 
Haven't had that one yet...

It adds a "" in a multi select parameter, or you've added this as a choice?

Which viewer are you using? The Active-X does the best job overall. I'm less experienced with the others, but I know that the first choice in a prepopulated parameter list will be passed by default if nothing is selected, and you can't select a blank unless it's been manually entered or it's in the drop down.

Try the Active-X viewer, other than an ugly parameter selection screen if you have multiple parameters, it's pretty good.

-k kai@informeddatadecisions.com
 
I too have noticed this problem. If "" is a valid entry I am not sure how you would handle this. On my reports there either needs to be a entry, or set to null. I considered it a "user training" issue. I can see how it happens, the system probably doesn't know how to send "''". Actually as I recall I tried this with " " and it acted as if I had sent "".. you might want to try it from that angle.

Lisa
 
If "" is a valid entry, check for it's existence and work accordingly.

(if {?MyParamater}[1] <> '&quot;&quot;' then...
{MyField} in {?MyParamater}
else
if {?MyParamater}[1] = '&quot;&quot;' then...
true)

The second IF helps with SQL being passed thru to the server, it seems you have to have an explicit qualifier and disqualifier.

This case would not build a record selection criteria if the 1st choice in a parameter is &quot;&quot;, but will pass along to the server any other choices.

Perhaps that willl help, I still don't understand if you're prompting for &quot;&quot; as a perdefined choice and it's just defaulting to it, or whether the report is inserting it because no choice was made.

-k kai@informeddatadecisions.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top