8 replies
by sgt_shultz
by andrew.czaja
by bob sellman
If this is needed, then the sure way would be to add a date/time column ("Last Change Made") to each table that needs to be tracked. Modify your application so that every time data is added the date/time of the addition is saved with the row of data, and every time the data is changed in a row, the data/time the change(s) is/are made is recorded.
If you know or keep track of the last date/time you worked with the database, then queries could be built to display all rows changed since that date/time.
In addition you might also want to have a table that recorded the latest date/time that changes were made by anybody to anywhere.
by andrew.czaja
by andrew.czaja
by timfox
Another option is to take a copy of the database before you distribute it and setup a comparison query on the data. Yes, this might seem labour intensive, but will provide an absolute picture of all rows changed since your last database copy.
Exactly how labour (and programming) intensive, depends on how (modular and generic) you implement this approach.
But, depending on your usage of this information, Bob's answer with a LastUpdated field is usually the preferred option.
Hope it helps
TimFox
by andrew.czaja
by andrew.czaja
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending