Version Control for MS Access: Using the MSAccess-VCS Add-in

[Josef P.]

To prevent the thread from Does Microsoft Access 2024 (Professional Plus 2024) Export Forms as Text for Re-Import? becoming too OT, I'll start a new thread.

@Josef P. Based on the name of addin (Version Control), I expected it to create seperarte backups on each run, to have a history of changes.
something like:

MyDatabase
     |
     |____ MyDatabase_20250311_101510
     |____ MyDatabase_20250401_112010
     |____ MyDatabase_20250501_081230
     ........

But unfortunately each time the previous version gets over written and to prevent this, I have to create the folder structure manually.
Is there any consideration to have a feature like this in future versions?

The msaccess-vcs add-in is particularly helpful when using a version management system such as Git, Mercurial, etc.

You can of course use it without, but I wouldn't recommend it, as I wouldn't want to do without its capabilities.

A few URLs for reading:

What's the Purpose of an Access Version Control Add-in?

Access version control add-ins are not a replacement for Git, Subversion, or Mercurial.

nolongerset.com

How to choose a source code control system for Access development

Guide on choosing a source code control system for Access development when starting from scratch or replacing Visual SourceSafe.

codekabinett.com

If you cannot/may not use a version control system, you need to think about when you want to make the backup of the folder. In my opinion, it is not advantageous to export every time, because msaccess-vcs has the great feature of not always having to export everything.

My usual way of working: I export regularly while changing something in an application.
If I want to save the exported state, I check it into the local repository.
Once the exported code has reached the state that it “works”, I not only check it into the local repo, but also synchronize it with the repository in GitHub, Azure devops, etc. (depending on the project).

 

[Josef P.]

To follow up on the idea of creating a backup of the folder:
For example, you could set a procedure name in the add-in option 'Run Sub After Export' to call a procedure from your application that copies the directory to a ZIP file.

Note: In my msacces-vcs fork, this would also work via an add-in


Nevertheless, I recommend thinking about Git & Co.
You do not need a server for Git. You can also use Git on your own hard disk.

 

[KitaYama]

I'll read the links and will be back if I have more questions.
Thanks for the new thread.

 

[GPGeorge]

I'll read the links and will be back if I have more questions.
Thanks for the new thread.

FYI: Adam Waller gave a presentation to our Access User Group on the JoyfullService VCS. It might add some flavor to your discussion.

 

[KitaYama]

FYI: Adam Waller gave a presentation to our Access User Group on the JoyfullService VCS. It might add some flavor to your discussion.

I appreciate the link.
I'm sure it has new thing to learn.

 

[Josef P.]

That will certainly be informative:

Access DevCon 2025 – Agenda

Access DevCon 2025 will take place on April 10+11. The conference agenda reflects the current situation and position of Access and VBA.

www.accessforever.org

Who is actually the referee for this duel? ... Karl?

 

[sonic8]

Who is actually the referee for this duel?

Attend and find out. ;-)

 

[Josef P.]

I was a little curious => Code to create backup of VCS folder:

Option Compare Database
Option Explicit

' insert this procedure name in VCS option "Run Sub After Export"
Public Sub RunAfterVcsExportProc()

    If MsgBox("Create backup of VCS folder?", vbYesNo, "VCS (Run After Export): " & CurrentProject.Name) = vbYes Then
        SaveExportFolderToZip
    End If

End Sub

Private Sub SaveExportFolderToZip()

    Dim ExportFolder As String
    Dim TargetZipFile As String
 
    ExportFolder = GetVcsExportFolder

    If Len(ExportFolder) = 0 Then
        Exit Sub
    End If
 
    TargetZipFile = GetTargetZipFile(ExportFolder)
    ZipWithPowerShell ExportFolder, TargetZipFile

End Sub

Private Function GetVcsExportFolder() As String
 
    Dim VcsExportPath As String

' Code to get ExportFolder from add-in:
' Bug in clsVersionControl ... terminate removes registry key and call ReleaseObjects, 
' so clsVersionControl can't run in multiple instances / a new instance can't used while exporting
'
'    Dim VCS As Object
'    Set VCS = Application.Run("MSAccessVCS.VCS")
'
'    If VCS Is Nothing Then
'        Err.Raise vbObjectError, "GetVcsExportFolder", "MSAccessVCS not loaded!"
'    End If
'
'    VcsExportPath = VCS.Options.GetExportFolder
'    If Right(VcsExportPath, 1) = "\" Then
'        VcsExportPath = Trim(Left(VcsExportPath, Len(VcsExportPath) - 1))
'    End If
'
'    GetVcsExportFolder = VcsExportPath
'
' => use default export path: CodeDb.Name & ".src\"

    GetVcsExportFolder = CodeDb.Name & ".src"

End Function

Private Function GetTargetZipFile(ByVal SourceFolderPath As String)
 
    If Right(SourceFolderPath, 1) = "\" Then
        SourceFolderPath = Trim(Left(SourceFolderPath, Len(SourceFolderPath) - 1))
    End If
 
    GetTargetZipFile = SourceFolderPath & "." & Format(Now(), "yyyymmdd_hhnnss") & ".zip"

End Function

Private Sub ZipWithPowerShell(ByVal SourceFolder As String, TargetZipFile As String)
 
    Dim PsCmd As String
 
    PsCmd = "Compress-Archive -Path '" & SourceFolder & "\*' -DestinationPath '" & TargetZipFile & "' -Force"
    PsCmd = "powershell -command " & PsCmd

    Shell PsCmd, vbHide

End Sub

Save RunAfterVcsExportProc in VCS option Run Sub After Export.

 

[KitaYama]

The msaccess-vcs add-in is particularly helpful when using a version management system such as Git, Mercurial, etc.

After going through your suggested links (and some other pages linked to them), I think I understand what you meant by above comment.

I'm off to read some documentation on Git to be sure I'm using it correctly and am not missing anything.

I also will watch the video suggested by @GPGeorge today during lunch time.

Many thanks to both.

Edit: I also appreciate the time you put on the code you suggested for zipping the exported files.

 

[KitaYama]

The msaccess-vcs add-in is particularly helpful when using a version management system such as Git, Mercurial, etc.

It appears that I had a lot of misunderstandings about Git & GitHub. Now that the clouds have been cleared and I have a better understanding of what you meant by above statement, I hope you don't mind two additional questions:

My usual way of working: I export regularly while changing something in an application.
If I want to save the exported state, I check it into the local repository.
Once the exported code has reached the state that it “works”, I not only check it into the local repo, but also synchronize it with the repository in GitHub, Azure devops, etc. (depending on the project).

Just to be sure I'm not misunderstanding you, it seems that you have two directories.
One for your regularly backup of the changes,
and another for your local repo, which later is used to be synced with GitHub,....

My question is
1- When you decide to copy the modified files from backup folder to local repo, how do you recognize what to be copied?
Do you copy all or only the modified files?
2- Is there any convenint way in MSAccess-VCS Add-in to select only modified objects to be exported? I'm afraid one's memory can not be relied on, and select only modified objects one by one. That is the main reason I normally export all objects.

Thanks again for your time.

 

[Josef P.]

1- When you decide to copy the modified files from backup folder to local repo, how do you recognize what to be copied?
Do you copy all or only the modified files?

There is only one folder for me. Git does the rest.
Git is a distributed version control system. In principle, the local repository is checked in first and this is later synchronized with a repository on a server.

2- Is there any convenint way in MSAccess-VCS Add-in to select only modified objects to be exported? I'm afraid one's memory can not be relied on, and select only modified objects one by one. That is the main reason I normally export all objects.

msaccess-vcs creates an index file with hash values in the local folder.
You can also always export everything, Git will recognize the differences in the files and only these will be taken into account in the commit.

A quick overview of routine tasks: