John,

Thanks for the idea. I will try this. I am surprised though that there isn't a system table that can be queried to get the answer. As a relative newbie to SQL Server (but not to sql) I thought it would simply be a matter of 'reading' the transaction log. But when I actually went to try to do this, I was baffled by the documentation, and couldn't actually find anything on how to do it. One of my books states that there is a system table 'syslogs'. It seemed like that if I queried this I might get my answer. But I couldn't find it anywhere. Upon further study of the SQL Server online help I read that the table syslogs was eliminated in SQL 7, and replaced by 'an operating system file'. But it gave no information on how to query/review that file or what the name of the file is or where it resides.


>David,
>
>One idea would be to add an Insert,Update,Delete (or you could break it up into three to determine when the last, Insert, Update, or Delete was done.) trigger to the table you would like to know this info, use the SQL GETDATE() function to store the current system date in a different table that you can query later.
>
>John
>
>>Now, however, I'm working with a SQL Server application. I don't know the application well, so, after I perform some function with it, I want to know what tables were updated - either delete, adds or changes.
>>
>>I would think this would be easy in SQL Server 7, but I can't figure it out. I can't find any system stored procedures, system tables etc. that store this.
>>
>>Thanks in advance for your help.
>>
>>David Schlesinger