Access 2013 + Source Control (Team Foundation Server) workflow

Question

Since Access 2013 is not any longer offering direct source control compatibility: how is your workflow to integrate a source code control into MS Access, especially TFS? Edit: workflow of access2013 -> ANY source code system appreciated

First thing I think of is exporting all objects into Text Files withe the builtin function SaveAsText which is available for almost every item in your database.

 Application.SaveAsText acModule, d.Name, sExportLocation & "Module_" & d.Name & ".txt"

I would load, save and maybe even check the plain files in with VBA functions. The question is: is there a better workflow for this task... I really doubt that this is the best way to integrate Access 2013 projects in Sorce control.

I heard of OASIS SVN but I think this is basically the same mechanism I would use.

Please tell me how you manage your access projects

Answer 1

I use OASIS-SVN here to export all objects in my access database file to be text files.

I then use git, souretree, etc...

It has worked well for me and has a number of settings that are useful (eg you can choose to export data, to export table links etc)

It is not ideal, but is manageable and better than nothing!

As you might expect, I use a git project and separate local directory for every access file.

Another option that is recently on the market can be found here "entAscc" now known as Ivercy!

This looks very promising as the source control is integrated into the development environment. I've not used it, but would like to!