Hi Inge,

>I do not quite understand. I can add a column to the table, and everytime a user (re)SAVE the record, I can update that column with the new date-time. I then have to check the original table every few minutes to see if the date-time column matches with what I have currently in my cursor. Is that right? Then, if not matching, I need to get new updated cursor: REQUERY() does not work with SQL PT cursor,so do I have to do another SQLEXEC to get a new fresh set of cursor?

you got it absouletely right! This is what I would do.

Ok, if you only have a small amount of data in your cursor you could just query your data again without any additional timestamp checks, but if you want to avoid unnecessary network traffic for larger resultsets, you better check for modifications first.

And you can use a trigger to update the "last change" column, so you don't have to manually update that column in all the places you're using one of these tables.

Regards,
Armin