>Has anyone figured out to get the Page Expiration thing to work? I have problems when users are allowed to update data, then push the back button and go back to previous data states, which don't jive with saved data. I would like users to get a Page Expiration notice when they try to go backwards, but since this is the web, I have no way of how they got to a page, by legitimate means or otherwise.

Hi Linda,

As some of the others indicated, expiring web pages can be problematic since it seems to work some times and not others.

This is a nutshell description, but you'll get the idea. In an application we have here I have resolved this issue by setting up a "session" on the back end by writing a record into a table with a unique ID when the user retrieves data for editing. The "session" id is loaded into the HTML returned as a hidden variable for later checking/verification.

When the data is submitted for saving, the "session" is checked for validity and the data saved or rejected based on this. When the data is saved, the "session" is ended by deleting the "session" record.

Basically I'm maintaining some "state" on the backend. The "session" record contains a datetime which is checked for timeout and updated on each hit so the user can keep the session "open" if needed.

Each night a procedure runs which clears out any "leftover sessions" older than the timeout period. The backend in this case is SQL Server but coulc be implemented with VFP backend.

I'm sure there are many ways to handle this scenario, I just mention my case to give you food for thought on how you will handle it.

Bill