ASP and Browser back button.

[Mike Berger]

I have a series of .asp pages that a user goes through to <I guess the
purpose really doesn't matter>.

On each page I have Response.Expires = 0 (which I understand to mean "do not
cache this page")

On PageInQuestion.asp (in the middle of the series) I use asp code to
generate a <select> box with numerous <option>'s, four <a>'s, and an <input
type=input> (this will become hidden when site is put in production). I read
some fields from a SQL server table to figure out what <option>'s to put in
the <select> AND what order.

The purpose of the <select> is to hold a bunch of fields, and the 4 <a>
tag's are <img url=UpArrow.gif ... DownArrow.gif ... DoubleUpArrow.gif ...
and DoubleDownArrow.gif></a>. So, the user can click on one of the "arrow"
..gif's, to move an <option> up, down, to top, or to bottom. I rearrange the
<option> contents in the <select> box via javascript. Pretty standard stuff.

The <input type=input> contains the text "field1, field2,
field3,...,fieldX". It is a comma-delimited string that is a list of the
entries in the <select>. As the user changes the order of the <option>'s in
the <select>, the contents of the <input> field change also i.e.
"field3,field1,field2,...fieldX".
As the user goes to the next page, I record any changes to the order in the
same SQL server table, based on the contents of the comma-delimited <input>
field.

So, my theory is, when the user goes to the next page and presses the Back,
since Response.Expires = 0, the .asp should be executed again. (Is this
assumption wrong ??)

Since, at the beginning of the PageInQuestion.asp, I read the SQL table to
get the order of the <select> <option>'s, I expected the ordering of the
<option>'s to be correct.

But, when I do a Back, the <select> box is displayed with the <option>'s in
the ORIGINAL order, not the changed order. But, the <input> has the CHANGED
order. This is acting like the browser is showing the cached, original
contents of the <select>, but not the <input>

I can't see any obvious bugs in my code, but that possibility exists. I most
likely have the wrong impression about how IE works. Can anyone shed any
light onto my predicament.

Hope this makes sense...

Thanks
Mike

[TomB]

This sounds like a job for aspfaq.....
http://www.aspfaq.com/show.asp?id=2022
"Mike Berger" <mb***************@skypoint.com> wrote in message
news:vv************@corp.supernews.com...

I have a series of .asp pages that a user goes through to <I guess the
purpose really doesn't matter>.

On each page I have Response.Expires = 0 (which I understand to mean "do not cache this page")

On PageInQuestion.asp (in the middle of the series) I use asp code to
generate a <select> box with numerous <option>'s, four <a>'s, and an <input type=input> (this will become hidden when site is put in production). I read some fields from a SQL server table to figure out what <option>'s to put in the <select> AND what order.

The purpose of the <select> is to hold a bunch of fields, and the 4 <a>
tag's are <img url=UpArrow.gif ... DownArrow.gif ... DoubleUpArrow.gif ...
and DoubleDownArrow.gif></a>. So, the user can click on one of the "arrow"
.gif's, to move an <option> up, down, to top, or to bottom. I rearrange the <option> contents in the <select> box via javascript. Pretty standard stuff.
The <input type=input> contains the text "field1, field2,
field3,...,fieldX". It is a comma-delimited string that is a list of the
entries in the <select>. As the user changes the order of the <option>'s in the <select>, the contents of the <input> field change also i.e.
"field3,field1,field2,...fieldX".
As the user goes to the next page, I record any changes to the order in the same SQL server table, based on the contents of the comma-delimited <input> field.

So, my theory is, when the user goes to the next page and presses the Back, since Response.Expires = 0, the .asp should be executed again. (Is this
assumption wrong ??)

Since, at the beginning of the PageInQuestion.asp, I read the SQL table to
get the order of the <select> <option>'s, I expected the ordering of the
<option>'s to be correct.

But, when I do a Back, the <select> box is displayed with the <option>'s in the ORIGINAL order, not the changed order. But, the <input> has the CHANGED order. This is acting like the browser is showing the cached, original
contents of the <select>, but not the <input>

I can't see any obvious bugs in my code, but that possibility exists. I most likely have the wrong impression about how IE works. Can anyone shed any
light onto my predicament.

Hope this makes sense...

Thanks
Mike

[Mike Berger]

Perfect !!!! Thanks Tom. A nice succinct answer to a long-winded
question.... :-)

Mike

"TomB" <sh*****@hotmailXXX.com> wrote in message
news:Os**************@TK2MSFTNGP12.phx.gbl...

This sounds like a job for aspfaq.....
http://www.aspfaq.com/show.asp?id=2022
"Mike Berger" <mb***************@skypoint.com> wrote in message
news:vv************@corp.supernews.com...

I have a series of .asp pages that a user goes through to <I guess the
purpose really doesn't matter>.

On each page I have Response.Expires = 0 (which I understand to mean "do

not

cache this page")

On PageInQuestion.asp (in the middle of the series) I use asp code to
generate a <select> box with numerous <option>'s, four <a>'s, and an

<input

type=input> (this will become hidden when site is put in production). I

read

some fields from a SQL server table to figure out what <option>'s to put

in

the <select> AND what order.

The purpose of the <select> is to hold a bunch of fields, and the 4 <a>
tag's are <img url=UpArrow.gif ... DownArrow.gif ... DoubleUpArrow.gif .... and DoubleDownArrow.gif></a>. So, the user can click on one of the "arrow" .gif's, to move an <option> up, down, to top, or to bottom. I rearrange

the

<option> contents in the <select> box via javascript. Pretty standard

stuff.

The <input type=input> contains the text "field1, field2,
field3,...,fieldX". It is a comma-delimited string that is a list of the
entries in the <select>. As the user changes the order of the <option>'s

in

the <select>, the contents of the <input> field change also i.e.
"field3,field1,field2,...fieldX".
As the user goes to the next page, I record any changes to the order in

the

same SQL server table, based on the contents of the comma-delimited

<input>

field.

So, my theory is, when the user goes to the next page and presses the

Back,

since Response.Expires = 0, the .asp should be executed again. (Is this
assumption wrong ??)

Since, at the beginning of the PageInQuestion.asp, I read the SQL table to get the order of the <select> <option>'s, I expected the ordering of the
<option>'s to be correct.

But, when I do a Back, the <select> box is displayed with the <option>'s

in

the ORIGINAL order, not the changed order. But, the <input> has the

CHANGED

order. This is acting like the browser is showing the cached, original
contents of the <select>, but not the <input>

I can't see any obvious bugs in my code, but that possibility exists. I

most

likely have the wrong impression about how IE works. Can anyone shed any
light onto my predicament.

Hope this makes sense...

Thanks
Mike