Version control for Microsoft Access development?

Question

We recently saw this message:

How do you use version control when developing Access?

Then we wrote the .vbs script from the example in this post to decompose the MS Access MS Access file.

The problem is that when I run the script in the .mdb file, I get the error message:

decose.vbs (71, 5) (null): Microsoft Office Access cannot open the database because it is missing or opened exclusively by another user.

Well, it has not disappeared and is not opened by another user. And there is no lock file associated with it.

Any idea what goes wrong?

Or is it easier to decompose our Access database for use in our version control software?

Answer 1

Ok

My boss found this: http://www.accessmvp.com/Arvin/DocDatabase.txt

And it works.

we added a new macro to the Access application and launched a new macro.

BOOM.

Everything is written out to our catalog.

So,

Answer 2

As already mentioned, mdb or accdb access alone is not a good idea to install under version control due to its binary format (no diff, no merging). When you have separate files, you can use any of the version control systems, because all of them can process files.

script Doug , / . OASIS, VBA Access v.v.

Mercurial, , . , Subversion Git, .

Answer 3

Cat Man, , VSS . , Team Foundation Server (TFS). MSSCCI Team Foundation Server 2010: http://visualstudiogallery.msdn.microsoft.com/bce06506-be38-47a1-9f29-d3937d3d88d6.

TFS Access 2007/2010.

Answer 4

:

': [Application.SaveAsText]

   [Application.LoadFromText]