On 5/25/06, Les Irvin <[EMAIL PROTECTED]> wrote: > What's the preferred concept in tracking database changes?
There are quite a few different methods of doing this, but you want to make sure that whatever you are doing is consistent. If you are using a database that implements triggers, like SQL Server, then you could create an audit trigger to write the changes to an audit table, and that would be implemented no matter where the query originated. If you don't have triggers available, or want to include other information with the audit (who edited it, etc.), then you should probably look at doing all of your database access through some kind of data access layer which implements the auditing across the board. -- Jim Wright Wright Business Solutions [EMAIL PROTECTED] 919-417-2257 Do you know where your towel is? http://www.towelday.kojv.net/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241495 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
