Michel:

Yes. I have learned that simply placing the cursor at end of URL and hitting return doesn't always mean another trip to server. If you want to force another trip to server, it appears you have to hit refresh button.

The web app I'm working on is an ad-hoc report engine working against a live database. Since database is pretty active, I would not want someone to attempt a refresh by hitting a return at URL and browser pulls up a cached page instead of re-running query. They could possible receive outdated information. I can force browser to always return to server by setting "force reload" parameter of ContentTypeHeader() or using StandardPage().

Thanx,
Charlie