What kind of database is it? When somebody adds or removes an object, you commit the change right? Then if people need to see the changes, they could click on a "Refresh" or "Get updated view" button, which selects the current table.

I would think one way you might could go about this would be to use autocommit of the transactions (inserts/updates/deletes/replacements), and an interface that either was user-driven for pulling updates (hit a button to check for updates) or timed to look for updates (such as a meta-refresh if the interface is via a webpage to pull the updates).

Hope that helps....

I will be using Access for the database. One option I was looking at was to send the user a message stating that there were changes to the the database. Should the user wish to proceed with the changes it would then refresh the screen for them. One other other options that I will be looking at is to wrap this whole project around a Tk interface so they would have no need to go to the website in order to do the modifications to the database. I guess where I am lost is I know I can get the user to the database and I can hold changes in a temp section and check to see if anyone else is in that table, etc. If they are not apply the changes to the table, etc. But what i would like to do is show the changes dynamically to everyone at onetime. Would it be more of a forced push on everyone? Or do you think that would be a good idea at all? Or would it be better to let the user have a choice and then when they go to publish their changes show them the current changes and then show them what their changes will effect? NG