SQLiteC-for-VBA VS msaccess-vcs-addin

Complete project source code with dependencies is available from the GitHub repo and the project documentation - from the GitHub pages site. I perform unit testing under x32/VBA6 (Excel XP/2002 SP3) and x64/VBA7 (Excel 2016) environments. With the entire repository cloned on Windows 10 and the two dependencies (the SQLiteODBC driver and the RubberDuck VBA add-in) installed, the following two quick checks can be executed right away from the immediate pane. This command ?LiteMan(":mem:").ExecADO.GetScalar("SELECT sqlite_version()") returns SQLite library version used by the SQLiteODBC driver (usually embedded), e.g., 3.23.3, and this command ?SQLiteC("").CreateConnection(":mem:").ExecADO.GetScalar("SELECT sqlite_version()") returns SQLite library version loaded by the project, e.g., 3.37.0. The project also includes a set of examples, which should also run out-of-the-box (see documentation).

I use Access VCS. You export the database, front end or back end to a folder and then add it to a git repo from there. It will not save the data only the code, macros, forms, reports, queries, and table schemas.

This is similar to what I was thinking of doing but was just curious if because of the way SharePoint works with the user directories if I could pop an update into the folder and it would resync with the new version whenever I may updates. If it doesn't indeed play well I've got a VBA script that checks to make sure the an FE file variable matches a table in the backend and if not prompts them to update to the newest version. I've also been using msaccess-vcs-integration and it's been a life saver.