Posting to another page

[Seboko]

Its very difficult to understand why .NET 1 does not easily allow posting a form to another page. I am using .NET 1 and really need to post to a different page developed by someone else who develops in php. He tells me he needs a form with certain fields. he will retrieve the fields and do whatever needs to be done and send me back the form.

The problem is that my page posted to itself. So I removed the runat attribute of my form. This resulted in the form being able to post to another page when the submit button is clicked, which was good. But I want to also write the information on the form to a database before sending out. This means I have to add the runat="server" to the submit button (so that I can add code to execute when this button is clicked). But clicking this button results in nothing happenning until I have added the runat="server" to the form - exactly what I was trying to avoid in the first place.

Having the runat="server" added to both my submit button and form results in data being written to the database when a submit button is clicked (which is what I want) but the form is not posted to this other person's page (which is not what I want).

Can you think of a way arround this???

[takkie]

Who said you cannot post a form to another page in .net?

You can write data to db in your code behind, and just do a regular asp post in the html side....

Or i didnt get what you mean?

i have seen this in action,

page1.aspx submits and writes information to database, and posting alot of variables to page2.aspx
page2.aspx request alot of variables, and display it page2.aspx accordingly. Page2 submits and write info to db, and post alot of new var to page3.
Page3 do the same thing as page2...

although this is not how .net app should work, but it does work...

-Tak

[sirpelidor]

i have seen this in action,

page1.aspx submits and writes information to database, and posting alot of variables to page2.aspx
page2.aspx request alot of variables, and display it page2.aspx accordingly. Page2 submits and write info to db, and post alot of new var to page3.
Page3 do the same thing as page2...

although this is not how .net app should work, but it does work...

-Tak


I think if he has no other options to go but to use the post method he metioned, it maybe easier for him to move back to traditional asp pages then sticking with aspx pages (unless there are features offered by .NET he really wants to utilize).

After all, even IIS understands vbscript between <% %> tag from a aspx page, it would be a waste for not using the .NET web form objects anyway.

[takkie]

I agree.