open a new window with Server.Transfer

[Yazster]

Hi All,

I'm hoping this is an easy one.

I have a form (EntryForm.aspx) for user entry, that contains many different parameter fields, as well as a lot of data inside each control.

I have another page (ProcessForm.aspx) that looks at the user input and runs the appropriate stored procedures and displaying features with Crystal/Excel.

Because of that amount of data in the entry form, I cannot pass parameters to the ProcessForm.aspx via the URL. We're also on a 3-server cluster, so any session variables will not necessarily be available to the processing page.

What I have is a button on the submit form that has SERVER.TRANSFER ("ProcessForm.aspx"), and I access the form controls directly from this page. This way, I don't have to worry about storing or passing values, I just read the form directly from the process page. I have to use SERVER.TRANSFER because I need to make sure that the server the user is on with the form is the same as the server for the processing page.

All of this works fine, but I want the process form to open in a new window, with the submit form remaining as is.

Is there any way to do this?

Any help would be greatly appreciated.

Many thanks,
Yazster

 

[ca8msm]

Why do you have two pages? Can't you just use the ASP.NET page the way it was designed and post back to itself?

--------------------------------------------------------------------------------------------------------------------------------------------

Need help finding an answer?

Try the search facility (

http://www.tek-tips.com/search.cfm)

or read FAQ222-2244 on how to get better results.

 

[Yazster]

The reason for the second page is that the page that processes the requests is a very generic design, handling more than 1 type of report. It's able to create Crystal Reports, Excel exports, on-screen displays (datagrid) and includes many supporting features (ie directory cleanup) that are common to all reports.

This way, each page is page is much lighter and allows us to focus on the UI for each situation, with the back-end functionally being centralized and out of the way.

 

[ca8msm]

OK, in that case you may have a bit of a problem in that if you want to open a popup window, you are limiting the number of possible ways to populate it's contents.

You've said you can't populate it's contents either with:

1) Session Variables
2) Querystring Variables

Which means the only other options I can think of are:

1) The Cache object (although I don't know if this would work because of your multiple server scenario)
2) Writing the data to a database/xml/text file (obviously some speed concerns may arise if you go this way)

Apart from that, I'm not sure how else you could go about it.

--------------------------------------------------------------------------------------------------------------------------------------------

Need help finding an answer?

Try the search facility (

http://www.tek-tips.com/search.cfm)

or read FAQ222-2244 on how to get better results.

 

[jhyde81]

You have a variery of options, but Server.Transfer is not one of them. It terminates execution of the first script. You could do things like open the window with javascript and reference the data between the parent and child windows, which, from the way you describe it, seems the most efficient. The child window upon opening could recurse through the DOM of parent to retrieve the values.

 

[RTomes]

You may to use something along the line of
javascript for an aspx page.

<input type=button value=submit onlick="document.forms[0].action='

http://YouOtherServer/reportpage.aspx';

document.forms[0].submit();">

You will have to iterate thru your form elemets on the accepting page using request.form("itemname")