Hi,

It sounds to me that it is a ASP/Database issue, and nothing to do with the servers, refreshing, cookies or HTTP configs. When you say the user has to close the browser and re-open - this starts a new server session, therefore data will be written to the database, and the user will see it.

We had this problem - inserting, or deleting data from a database, then go to another page to view the result - and get the old data. The problem was down to our connection to the database.


For example ....


Dim objConn
Dim objRst
Dim strSQL

Set objConn = Server.CreateObject("ADODB.Connection")
Set objRst = Server.CreateObject("ADODB.Recordset")

objConn.Open "DBQ=" & Server.Mappath("../../../databases/PCM.mdb") & ";Driver={Microsoft Access Driver (*.mdb)};"

'
strSQL = "YOUR SQL STATEMENT HERE"

objRst.Open strSQL, objConn , 1, 3 <####
objRST.CacheSize = 1


The line that I've marked above "objRst.Open strSQL, objConn , 1, 3 " it the line that opens the recordset, sets the cursor, and connection type.

To me, it sounds like you've set your cursor wrong. The above line sets the Cursor to 3, meaning dynamic. That way I can go up and down the recordset, and view changes to the DB in real time.

It's all to do with how you connect to the database

<%
Response.ExpiresAbsolute = Now() - 1
Response.AddHeader "Cache-Control", "must-revalidate"
Response.AddHeader "Cache-Control", "no-cache"
%>

It seems to work OK for me, perhaps you have a server cache issue?