We have some jokers on here today.<BR><BR>Right...<BR><BR>The Response.Redirect does not do what the html <a href='whatever.htm'> does. Response.Redirect returns a HTTP redirect (200 I think), which causes the browser to go and load another page rather than this one.<BR><BR>The HTML link is interpreted by the browser. If you have frames, or named child windows, you can target that link. Basically, the browser sees you clicking on the link and says "where do i show that page?". If no "target" is specified, it is the current frame or whereever the base target is.<BR><BR>In the Response.Redirect idea, the browser has already decided WHERE it is going to show the page, and it is now looking for WHAT to display.<BR><BR>Try writing out<BR>==== START<BR><script>parent.framename.locati on.href='x.asp';document.location.href=& #039;y.asp';</script><BR>==== END<BR><BR>There's no way to do it using your initial example.<BR><BR>Craig.