Update button not redirecting to correct page

Hi - I hope this is an easy solution - I've been trying to get this to work all morning, but no luck, so please help. Quite simply, I want the update button (and the cancel button) on my inventory_Update.php page to redirect to order_Detail.php after update. I've passed the orderID in the query string and the cancel button redirects fine however the orderID doesn't carry over on update. Please tell me what I'm doing wrong. Relevant pages attached.

the redirect querystring is getting the ID from the rsOrders recordset
$WA_redirectURL = "orders_Detail.php?OrderID=".$row_rsOrders['OrderID'] ."";



the rsOrders needs a OrderID querysting to be passed into it to filter correctly, but the forms action does not pass this in:

<form  action="inventory_Update.php?InvID=<?php echo(rawurlencode($row_WADAinventory['InvID'])); ?>" method="post" name="WADAUpdateForm" id="WADAUpdateForm">

change the form tag to:

<form  action="inventory_Update.php?InvID=<?php echo(rawurlencode($row_WADAinventory['InvID'])); ?>&OrderID=<?php echo(rawurlencode($row_rsOrders['OrderID'])); ?>" method="post" name="WADAUpdateForm" id="WADAUpdateForm">

thats brilliant and all fixed - thanks so much.

you're welcome.

Actually wanted to add to this, as having done a bit of googling this seems to be a fairly common query, but havent' managed to find the answer. Although the code you gave worked a treat on my local server, when I uploaded to my remote server on update I got the following message:
The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay.

Is this something that I can fix within the page code or do I need to contact the hosting provider?

Thanks again.

my guess is that the problem is being caused by this part of the rsItems recordset:
WHERE items.ItemBrandID=brands.BrandID

It seams odd to me that only one join on the page would cause this error.


try taking that out, and see if the error goes away.

Ultimately, to fix it you will need to contact the host, but if removing that part of the where clause fixes the error, at least you will now that whatever restriction the have for the max join size is ridiculous since recordsets with one, 2 or even 4 joins are very commonplace.