Transfering Variables, But Using Response.Redirect

I have a page that contains a link. When a user clicks the link, the link runs a new page that the client does not see (i.e. server side only). The new page looks at a database to see if certain conditions are true. If they are, it updates the database and redirects the user back to page 1, where the client will see the updated information.

However, if the database conditions are false, the client will be redirected back to page1, but will have an error message saying that the database could not be updated.

So overall it looks something like:

PAGE1 ----> DATABASEUPDATER(checks conditions)

IF CONDITIONS=TRUE THEN
UPDATE STUFF
RESPONSE.REDIRECT(PAGE1.ASP)
ELSE
DONT TOUCH DATABASE
RESPONSE.WRITE("conditions have not been met")
XXXXXXXXXXXXXX
END IF

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

My problem is deciding what goes in the XXXXXXXXXXXX section.

I have looked for other examples of this but I could not find something this specific....

If i use Response.Redirect, the explorer will go back to Page1.asp but will not display the error message and the client will not be aware that there is a problem.

If I use server.transfer (to put control back into the hands of page1.asp) or server.execute (to just run Page1.asp within the current script) the actual page that the user is looking at is not Page1.asp - they are actually looking at DatabaseUpdater.asp with Page1.asp executed inside it....unfortunately I require it to be Page1.asp itself, which is why i cannot work out what to put there.

Looking at other threads on similar topics, it might be possible to add something to the session variables or something and then get Page1 to look for whether a certain thing is written as a session variable (if that makes any sense!)