This may not be true in your case, but I remember another user on this list claiming a similar thing, and his problem was actually code-related. He had his db update code *AFTER* the results were displayed (ie. doing edit and save on same page).
Check your programming logic. Just a note to people out there who may not have much programming experience - try doing all of your server-side processing (or at least db and filesystem calls, etc) before you output any data, this way you can implement error checking etc and still use the header() function, etc. Adam --- Original Message --- Hello, I don't know if this is the right list to send this question to. It appears that the browser caches the result after a PHP page updates the database. I have to manually reload it in order to see the updates. Does anyone know how to overcome this? Thanks, Philip