Ability to Manually Enter a Parameter in a Queried Parameter

I have a queried parameter getting it's parameters from its own dataset.
Works great. Now they want to have the ability to enter their own if they
know what value they want rather than scrolling through the list.
Any ideas on how to go about this?
ThanksAnybody?
"BillD" wrote:
> I have a queried parameter getting it's parameters from its own dataset.
> Works great. Now they want to have the ability to enter their own if they
> know what value they want rather than scrolling through the list.
> Any ideas on how to go about this?
> Thanks
>|||Chris,
Thank You for taking the time to reply. Looks like I'll be getting into some
ASP as I also like to have a calendar for date parameters...
"Chris Baldwin" wrote:
> > "BillD" wrote:
> >
> >> I have a queried parameter getting it's parameters from its own
> >> dataset. Works great. Now they want to have the ability to enter
> >> their own if they know what value they want rather than scrolling
> >> through the list.
> Hello BillD,
> I'm not sure there's a way to do this when rendering through Report Manager.
> If there is I'd love to hear about it. But, I know you could easily create
> a custom webform that accomplishes this goal.
> For example, you can use JavaScript to determine whether the text box has
> been typed into and adjust the form action that requests the report accordingly.
> Here's a snippet that I used in one of my apps that might help:
> <script>
> function process()
> {
> var actionBase = "http://localhost/reportserver/myreport?rs:Command=Render&ParamVal=";
> var theForm = document.getElementById("myForm");
> var txtBox = document.getElementById("myBox");
> var selectBox = document.getElementById("mySelect");
> // If the textbox is empty, use the select box value
> if(txtBox.value == "")
> theForm.action = actionBase + selectBox.value;
> else
> // otherwise, use the text box value
> theForm.action = actionBase + txtBox.value;
> theForm.submit();
> }
> </script>
> <form method="get" id="myForm">
> <select id="mySelect">
> <!-- would be populated from database -->
> <option>Val1</option>
> <option>Val2</option>
> <option>Val3</option>
> </select>
> <input id="myBox" type="textbox">
> <input type="button" value="Submit" onClick="process();">
> </form>
> -chris
>
>sql

A transport-level error has occurred when sending the request to the server. (provider: TC

when i enter the user name, Password and click enter in my site

it showing below error..

A transport-level error has occurred when sending the request to the server.

(provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

What may be the problem..

This does not sound like a SQL Server problem, it's more likely something is acting up in the network.

Have a look at 2 links below if it still fail after few retries:
http://www.mcse.ms/message2316445.html
http://channel9.msdn.com/ShowPost.aspx?PostID=243278

|||

i am accessing the site through internet..

if i reload the error page it loading successfully..

sql

A problem with polish Chars.

Hi guys,

I got a big problem with my SQL 2000 DB, I got to enter polish chars in the fields and I don't seem to be able to. I tried setting the collation to SQL_Latin1_General_CP1250_CI_AS or SQL_Polish_CP1250_CS_AS or used the window collation in polish on the separate fields, I tried setting my new DB collation to SQL_Polish_CP1250_CI_AS. But nothing helped I tried to insert the phrase "Wyda?e? 200 punktów na gr? w ping-ponga." but every time the special chars like the "?" or the "ó" are gone and become normal "e" or "o".

Could somebody help me here cause I'm really not getting out of this one.

Hi!

Posted elsewhere by Dejan Sarka, SQL Server MVP :

"In SQL 2000 you can define collations on server, db and column level. This collation is used, for example if defined on column level for a varchar column, on all rows. If you need different collations in different rows of the same column, then you have to use unicode data types, in the example nvarchar. So, check the collation on all levels - server, db and column."

A problem with polish Chars.

Hi guys,

I got a big problem with my SQL 2000 DB, I got to enter polish chars in the fields and I don't seem to be able to. I tried setting the collation to SQL_Latin1_General_CP1250_CI_AS or SQL_Polish_CP1250_CS_AS or used the window collation in polish on the separate fields, I tried setting my new DB collation to SQL_Polish_CP1250_CI_AS. But nothing helped I tried to insert the phrase "Wyda?e? 200 punktów na gr? w ping-ponga." but every time the special chars like the "?" or the "ó" are gone and become normal "e" or "o".

Could somebody help me here cause I'm really not getting out of this one.

Hi!

Posted elsewhere by Dejan Sarka, SQL Server MVP :

"In SQL 2000 you can define collations on server, db and column level. This collation is used, for example if defined on column level for a varchar column, on all rows. If you need different collations in different rows of the same column, then you have to use unicode data types, in the example nvarchar. So, check the collation on all levels - server, db and column."