Version Control in Access??

[guixian88]

Hi all...

I've got a little question, really hope someone can help me out.

Does anyone know whether it's possible to implement version control of an Access database?

As in, every change that is made (e.g. add new record, modify record) is not done directly to the database, but a new version of the database is created with the changes.

So, in the end, you can keep track of the changes you made to the database.

Anyone have the answer? Thanks...

 

[WayneRyan]

guixian,

You can apply version control to both software and data.

With software there are many 3rd party packages that define software
configuration elements and allow for tracking their evolution. It is easy to
look at various code/forms and see how they have been changed for
enhancements/fixes.

With data, the transformation is much harder to track, and I don't know
offhand of any off-the-shelf s/w available. Usually the goal towards
definition of databases just involves a static collection of the tables,
relationships, permissions, and the data. You can spin off multiple copies,
which become candidates to be the next baseline.

If you're addressing the "mechanics" of the evolution, it's possible to do
something like generate the SQL that could be applied to the DB, and not
actually change the data itself.

But that is a LOT of work!

An easier method might to (after the fact) defineall of the table
additions/deletions/updates that were made between the two versions.
You can do that pretty easily with queries.

Just some thoughts.

Wayne

 

[guixian88]

hi wayne,

thanks for replying, but i don't quite understand ur reply... but basically, what i wanna do is to keep track of the changes to the database...

say record ABC has been changes to ABD... if another user come along....he should not only know that a change has been made.. but wat the original value of D was...

on another forum, someone suggested to me to build a history table, and jz log every new record... but i dunno... there are so many issues... like, how do i keep track of the user that changed the record, and i would also need to keep track of new records... that wouldn't be possible would it?

if a user added a new record, how would the next user know that that record was new and had not jz been there all the while?

wat do u think??

 

[WayneRyan]

g,

What you're talking about is an audit trail. You can
use the search facility here and should find something.

Be prepared for a little more effort than you think
this will require.

Access is very adept at saving data. You will to
intercept all DB updates to log the User, Action,
Time and other pertinent info.

If you have something "fall through the cracks", like a
form that updates a table that its not bound to, then
your Audit Trail weakens.

Also bear in mind that Access doesn't support data-bound
triggers. The Audit Trail can be compromised by any
user manipulating tables directly (database view) or
externally (thru ODBC).

Hope to hear back on your progress.

Wayne