Do you need form elements on the input.asp page to be filled in with the values previously entered?
I am trying all sorts of tests and can't figure out anything right now.
My instinct, then, is to make your 'back' button on the error.asp page call a function which actually goes forward, calling input.asp with a URL parameter (e.g., document.location = 'input.asp?dis=F';), catch that in the input.asp page and use the BODY tag's onload event to UNDISABLE certain form elements if the URL parameter value was F.
Anyone else?
--Dave