By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,491 Members | 879 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,491 IT Pros & Developers. It's quick & easy.

Subversion and splitting apart MDB files for better version control in VBA for Access?

P: n/a
My company I work for uses VBA for Access to program one of our
projects. We just now set up the Subversion version control system for
our various projects.

It works great for our VB6 and .NET work, of course, but our main
program is still in old VBA, all of the front-end code is in one
database file. Not only does it take a while to commit changes to the
repository, but it also somewhat defeats the purpose of the using SVN,
since we probably would have to manually merge every change we make if
more than one person decides to work on the code.

Is there any way that we could break up the code? Is there a command of
some sort in Access where you can take all of the forms, modules, etc
out of the MDB file into the same folder to store in the repository? Or
is there any other good way to handle the situation? If anyone knows
the best way to split the database up to better handle version control,
it would be very helpful.

Shawn Axsom

Jul 18 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
We use Visual Source Safe for version control for MS Access. Works
fine, though it's a pain in the a&&, as I assume all version control
is.

Jeremy Wallace
Fund for the City of New York

axs221 wrote:
My company I work for uses VBA for Access to program one of our
projects. We just now set up the Subversion version control system for
our various projects.

It works great for our VB6 and .NET work, of course, but our main
program is still in old VBA, all of the front-end code is in one
database file. Not only does it take a while to commit changes to the
repository, but it also somewhat defeats the purpose of the using SVN,
since we probably would have to manually merge every change we make if
more than one person decides to work on the code.

Is there any way that we could break up the code? Is there a command of
some sort in Access where you can take all of the forms, modules, etc
out of the MDB file into the same folder to store in the repository? Or
is there any other good way to handle the situation? If anyone knows
the best way to split the database up to better handle version control,
it would be very helpful.

Shawn Axsom
Jul 18 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.