Hi,
I have a drop down list in my .aspx page. When clicked the last item in the list needs to open a new window and display an external website. I know I can't open a new window server side and need to use a script on the page but don't know how. Ideally the script would be an IF statement - if the last index of the list is selected then new window opens.
Any suggestions / help?
Thank you.

"I will prepare and one day my chance will come."

__________________
\"I will prepare and one day my chance will come.\"

You can open a new window server side, sort of.

Enable AutoPostBack on the ddl and in your event handler do this:

if(ddl.SelectedItem.Value == "someValue")
{
     string js = "<script language='javascript'>";
     js += "window.open();"
     js += "</scr" + "ipt>"; //the end tag must be formated like this
     Response.Write(js);
}

hth.

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
Technical Editor for:
Professional Search Engine Optimization with ASP.NET

Professional IIS 7 and ASP.NET Integrated Programming

================================================== =========

you can also use javascript to open the new window. If you are looking for javascript solution, let me know.

Thanks dparsons,
that worked. Much appreciated.

Steve

"I will prepare and one day my chance will come."

parsons, what's the significance of above?

Regards
Mike

Don't expect too much, too soon.

For some reason if you try to write out the end tag as "</script>" you will get a Javascript syntax error error everytime it is wrote to the response stream, regardless of syntax validity.

The reason for this error has something to do with the javascript functions that the runtime adds to the page to enable postbacks and such, but I can not remember exactly why this problem occurs. In any event, this is the work around to that problem. ^^

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
Technical Editor for:
Professional Search Engine Optimization with ASP.NET

Professional IIS 7 and ASP.NET Integrated Programming

================================================== =========

ok, thanx for the information parsons, I'll keep this in mind...

Regards
Mike

Don't expect too much, too soon.

Actually, it has to do with the server side scripts, and only with pages without code behind (and with classic ASP pages).

With a page with in-line code or a classic ASP page, all server side code is wrapped in a <script> element like tis:

<script runat="server">
  protected void Page_Load(object sender, EventArgs e)
  {

  }
</script>

Now, imagine you had your script without the split end tag. You'd end up with this:

<script runat="server">
protected void Page_Load(object sender, EventArgs e)
{
  string js = "<script type=\"text/javascript\">";
  js += "alert('Something');";
  js += "</script>";
  Response.Write(js);
}
</script>

With color coding on, you immediately see what's going on. All the code is black, except for the *first* </script> tag which is seen as the closing tag for the *server side script element*, and not as a part of a string literal.

Splitting up the end tag like Doug suggested fixes the problem. The first closing script tag is now seen as a string literal, while the second one is used to close the actual <script> element.

AFAIK, you only need this in pages with in-line code or in classic ASP pages. Pages with code behind don't suffer from this problem as there's no <script> element anywhere....

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004