Can you use source control with VBA?

[Eric B.]

Hi,

My knowledge of VBA development is still rather limited, so forgive me if
this sounds like a silly question. I am trying to figure out how to use
version control software (CVS or VSS) during the development my my
Access/VBA application.

I have only recently started programming in MS VBA, and am still somewhat
limited in my knowledge of VB (the last time I touched VB was 10+ yrs ago).
The only way I know to access the Access VBA code is to open the mdb in
access, and from there open the Visual Basic Editor (version 6.5). When I
save the VB code, it saves it within the MDB file.

I have used CVS for years already (and VSS prior to my switch to CVS) with
my PHP, HTML & Java code and love it. Recently, however, I've been starting
to work with VBA apps - specifically, an MS Access database application.
I'm stuck, however, trying to understand if/how there is a way to use source
control on my VBA code in the MDB application.

I realize that I can check in and check out the entire MDB every time, but
that seems extremely inefficient - both in terms of space (it is a binary
file, so would have to checkin over a meg every time), and in terms of
source control - I won't be able to see differences between versions, or
roll back and forth easily, etc... Especially when there are several
modules & classes, it would mean that I can't source control any 1 class or
module individually.

Does anyone have any ideas how (or even if) it is possible to use Source
Control on VBA files? I can only imagine this would apply to any MS
product - like Excel, Access, Word, etc.... I can't imagine all the VBA
applications out there were designed without it...

Thanks for any advice or suggestions you can offer!

Eric

 

[Albert D. Kallal]

Microsoft's VSS (Visual Source Safe) work with ms-access.

And, it allows you to check in, and out INDIVIDUAL things like
reports, or forms, or even sql quires can be check in and out
(really amazing actually).

so, source code control works just fine with ms-access. Just like any source
code
control system, you have the ability to "build" or "run" that resulting
application on
your computer..and creating a mdb out of this is not a different process at
all.

Before I send you off on the links for using VSS, you should be aware of
how the general software development process works for ms-access.

So, give the following article a read...you need this general knowledge
before
you jump on the VSS (visual source safe) bandwagon..

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

I realize that I can check in and check out the entire MDB every time, but
that seems extremely inefficient

No, when you use VSS, you check in/out individual items. Most source
code control systems check in/out individual items..but you still have a
*local* build of the current project on YOUR pc. The fact of having
15 files separate, or moving 1 file into a mdb file that "contains"
15 files is really much moot point on a conceptual level. In both
cases...you have pieces that you move from the source safe
to your application....


here is the info you need for a2003:

Info linik

http://support.microsoft.com/kb/837136/en-us

Download page:
http://www.microsoft.com/downloads/...f4-a916-48c5-8f84-44b91fa774bc&displaylang=en

Here is some pictures..and if you look close, you can see items that are
locked, or checked out by you:
http://www.members.shaw.ca/AlbertKallal/vss/index.htm

So, the Microsoft Visual Source Safe does work with ms-access, and it allows
more then one
developer to work on the same application.

 

[mtnbiker2.0]

Microsoft's VSS (Visual Source Safe) work with ms-access. ....

http://support.microsoft.com/kb/837136/en-us

Download page:http://www.microsoft.com/downloads/details.aspx?FamilyID=2ea45ff4-a91...
....
So, the Microsoft Visual Source Safe does work with ms-access, and it allows
more then one
developer to work on the same application.

Eric,

Albert is exactly right in pointing you to the Access Source Code
Control Add-in. It will do what you are looking for with .MDB files.
But do yourself a huge favor and try out Evolution, http://www.ionforge.com/downloads
, and save yourself the grief of re-learning to hate SourceSafe.
ionForge gives away a single user license for free, and I've
personally seen the Access Source Code Control Add-in used
successfully with it.

Paul

 

[Eric B.]

Eric,

Albert is exactly right in pointing you to the Access Source Code
Control Add-in. It will do what you are looking for with .MDB files.
But do yourself a huge favor and try out Evolution,
http://www.ionforge.com/downloads
, and save yourself the grief of re-learning to hate SourceSafe.
ionForge gives away a single user license for free, and I've
personally seen the Access Source Code Control Add-in used
successfully with it.

Paul

Excellent. Thanks guys! That was the missing link / puzzle I was looking
for. I played with it quickly with VSS6, and I agree - it isn't something I
particularly want to relearn to hate. I have become very content with CVS
and ideally would like to use it, the only problem is that the CVS SCC
plugins I have found don't seem to be all that stable. I'll report back
once I find a good compromise.

I did take a quick look at Evolution, and it defnitely seems interesting,
however I'm not sure I'm ready to move over to another source controller
yet. But then again, if I can't find a good CVS SCC plugin, I just may very
well need to move to something else, so might as well be Evolution.

Does everyone else here use VSS for version control?

Thanks again for all the help!

Eric

 

[Albert D. Kallal]

Albert is exactly right in pointing you to the Access Source Code
Control Add-in. It will do what you are looking for with .MDB files.
But do yourself a huge favor and try out Evolution,
http://www.ionforge.com/downloads
, and save yourself the grief of re-learning to hate SourceSafe.
ionForge gives away a single user license for free, and I've
personally seen the Access Source Code Control Add-in used
successfully with it.

Very neat-o...

I have heard good things about Evoluiaton. I not used it, but, that sounds
likely a very cool tool to try....

The fact that you can use a server based system, means that you could
collaborate on a ms-access project over the web
with developers in different locations.......