Git and Mercurial repositories don't mix well with cloud drives like OneDrive and Dropbox. Here are two alternative approaches to keep you out of trouble.

Helix TeamHub is the obvious choice for Mercurial repository hosting for solo Access developers and small teams.

With this step-by-step guide, you'll be using version control with Access in under 20 minutes.

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

Unfortunately, choosing the less popular version control system has some important real-world drawbacks.

This classic article from fifteen years ago contains one of the most impressively specific (and accurate) technology predictions I've ever read.

Reassembling the pieces of a fragile system is a fool's (horse's?) errand. Turning back the clock is a more reliable fix.

Why use text-based version control for visual objects like forms and reports? I'll tell you why, but first, find all the differences between these two pictures...

Curious about getting started with version control in Microsoft Access, but don't want to commit a lot of time or money? This could be just the solution for you.

Using Version Control in Access is like having a time machine that makes it easy to undo design mistakes. Here's a quick overview of the process.

How can you figure out what you changed on a form when you can't remember changing anything on that form? Version control, of course.

"Do you want to save your changes?" No, not if I just added temporary debugging code. But, Yes, if I also added production code. What to do?

If it can cause a bug in your software, you should be tracking it in version control. Database schema changes absolutely fall into that category.

I had to update the settings file for 120 Mercurial repositories. I saved hours of tedium using a regex in the "Find in Files" feature of Notepad++.