My preferred approach to version control with Microsoft Access is to use the undocumented SaveAsText and LoadFromText methods. I wrote a series of articles describing this approach.
I love the workflow I built for myself and my team. In its current form, though, it is a one-size-fits-one solution. I still have not written a full implementation guide for how someone would integrate my solution into their own workflow. Suffice it to say that such a guide would involve many steps.
A quicker way to get started
The project README has a great getting started gif:
Focus of this fork
There are several forks of Brendan Kidwell's original msaccess-vcs-integration project. I'll let Adam Waller's README explain what sets his fork apart from the others:
Since there are several forks of this project on GitHub, I thought it might be helpful to give some insight into the long-term direction I am taking with this fork. Below are some of the changes I am looking to implement in the future:
- Finish an automated testing process where a complex sample database can be exported, reconstructed, exported again, and compared with the original export to ensure that the build process is fully constructing the database from the exported source files.
- Build out an automated deployment workflow using a GitLab runner that is triggered on a commit to automatically build, test, and deploy a database project. Discussion on this idea can be found here.
The Access add-in itself is not a version control application. It "merely" exports the Access objects into a series of plain text files. To finish the process, you will also need a standalone version control system, like Git or Mercurial.
What do you use?
Do you use version control with Microsoft Access? If so, what solution are you using? Let me know in the comments below.