>Thanks Kevin.
>
>Unfortunately the environment I'm working in a the moment is about as likely to let me create triggers as make me King of England.
>

Only other option then...although it's risky

Starting in SQL 2005, you can slap an OUTPUT INTO statement at the end of any DML statement. The OUTPUT statement will let you tap into the INSERTED and DELETED tables.

So theoretically, you can capture changes using OUTPUT INTO , as part of the INSERT/UPDATE/DELETE statement.

However, this will only work when you control the inserts/updates/deletes across the board.

If someone goes into SSMS and changes data manually (or maybe you have legacy jobs that touch the data and you can't change the source of those jobs), then changes in those scenarios won't be captured.

So OUTPUT INTO can be risky as a full blown audit trail tools.