Marge Gunderson wrote:
<to*******@gmai l.com> wrote in message
news:11******** **************@ g43g2000cwa.goo glegroups.com.. .
Hi All,
We are hoping to setup source control for our Access XP development.
We don't want to use Visual SourceSafe because (a) we often work
remotely and (b) we hear bad things about SourceSafe.
Are there any alternatives to SourceSafe? I have been looking into
Vault, Subversion and Perforce, but nobody seems to support source
control in Access.
Should we just bag this idea and wait until we start developing in a
"real" tool? (not any time soon, as we have a lot of code in Access)
Ideas? Any info much appreciated.
Thanks,
-Tom
Bag this idea and use a "real" tool.
Some of these have "real" newsgroups
With "real" helpful answers
gack! Version control with Access!
multi-developer work with Access! Gack! If multiple people are working
on the same MDB file (as opposed to local copies), only one will have
"exclusive access" to the DB w.r.t forms/reports/vba...
Be that as it may, you might be able to sort of roll your own. There are
a couple of slightly undocumented functions that let you dump/export VBA
code well.
I don't version control my work, sort of copying and pasting objects (to
make a backup, then renaming it better).
Even with SourceSafe, it sucks (Modules/Forms/Reports get saved as one
entity...), and that's probably the best "integratio n" with Access.