Im assuming your second form is on a second page because you cannot have multiple forms on a page...
There are several ways to do this:
1. Via request:
C#
string url = "yourpage.aspx? Textbox=" + YourTextboxId.T ext;
Response.Redire ct(url);
HTML
<asp:TextBox runat="server" id="YourTextbox Id" ... ></asp:TextBox>
...
Waazzzii
Last Activity: Oct 2 '08, 03:17 PM
Joined: Jan 15 '08
Location:
-
BankLogoImage.I mageUrl = SmartecLogoImag e.ImageUrl;
When you specify the asp Image tag you need to state the attribute 'ImageUrl=""' otherwise server side will not recognise it as being defined- this is most likely why you cannot change the value of it from the server. If you are using a regular html tag with the 'src' attribute then this will fail...
Can you show your html code?Leave a comment:
-
It looks like most of your tables and buttons are generated server side... Every time a page is posted back to, it acts as a 'refresh' in a way, so any value that was stored previously will be erased since the elements are re-populated.
If you are using postbacks try using session state (or even better viewstate) to store the information. Possibly even create a list of the parameters you need, then store the list in a single viewstate...Leave a comment:
-
Found a workaround- for some reason once the NewTransaction page had been rendered, the OrderBasket page contents from prior were being rendered over it. Not the best solution but a simple "this.Visib le= false" after the transfer (in the buttonConfirm_C lick method) did the trick.Leave a comment:
-
The NewTransaction page is ok and does load properly, only when the Server.Transfer is used does the page show up blank. The Server.Execute method effectively executes the code, but then returns back to the orderbasket page after a brief display of the newtransaction page.
OrderBasket.asp x.cs:
protected void buttonConfirm_C lick(object sender, System.EventArg s e)
{
//Add the transactiondeta ils...Leave a comment:
-
Server.Transfer [System.Threading.ThreadAbortException] Blank Page
Here's an interesting one... received the {Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.} exception when attempting a Server.Transfer ("Page.aspx" ). This came about when i upgraded from VWD 2005 to VWD 2008, but kept the .NET framework 2.0 (instead of moving immediately to 3.5).
I have a master page controlling the orderbasket.asp x page, and it is from the orderbasket.asp x...
No activity results to display
Leave a comment: