Hi Tamar,

The workstation that needs to know about changes does indeed make changes. They have a Refresh button on their screen that is disabled if they also have changes pending. So they have been taught to save their changes every now and then and then a requery is done on their view. I was trying to work into their screen something a bit more informative. It actually does have that a bit - I have a timer that checks for new records in the table every few minutes and if it has changed from the time they did their last requery, it displays a label at the bottom of the screen letting them know that. They then typically will save what they are doing so they can see the new record.

This might end up being too much work to signal them about changes in current rows when they also have changes. It might end up being that I just tell them to keep doing what they are doing - save your own changes regularly and then you will see changes anyone else has made.

Thanks for the input all!
Albert

>
>If you're working with views, won't calling Requery for the view give you what you need? As I understand your situation, the workstation that wants to know if anyone else has changed anything won't have made changes, so you don't have an issue of uncommitted changes. You just need to ensure you have the most recent data, right?
>
>Tamar