I have a set of password protected .asp pages that read data from a database and use a session variable to maintain state. On one page, the user submits a form and a table (SQL) is updated. This same page dispays the data from the table that will be updated. After the user submits the update, and returns to that page via links on other secured pages the output is not updated with the new data (if refresh is pressed then the new data is shown). Apparently the page is being cached on the client machine by the browser. I had the idea of puting a timestamp on the end of the links to make the browser think that the page is different and then it will refresh the page. I thought this was the greatest solution but it does not work on Macs with Netscape (parameter incorrect error).<BR>At the top of every have I also have:<BR>Response.ExpiresAbsolute = Now() - 1<BR>and <BR><meta http-equiv="expires" content="-1"><BR><meta http-equiv="pragma" content="no-cache"><BR><BR>Here is the example of my url with timestamp.<BR>http://www.workoutsforwomen.com/accountability.asp?10/6/2000%203:17:13%20PM<BR><BR>I was thinking of using a random # instead but I do not know if that will make any difference. <BR><BR>All of this is hard to test since I only have access to mac/netscape via my customers.<BR><BR>The final question. How do I get the pages to load every time they are requested? <BR><BR>Thanks!!!!