Versioning/tracking changes

P

Poseur

Apparently a rudimentary environment like the VBE does not have
any way to track changes to modules nor can I find any plug-in
or add-on to do it.
Anyone have a system worked out?
I'm constantly changed and tweaking my projects and I do it at
home and at work so I send my files back and forth and I'm
constantly getting confused about which is which version or
latest good revision.
BTW, the email server at work does not allow .bas extension
attachments thru - so I just change them to .txt for the trip.
 
M

Myrna Larson

I export the module as a BAS (text) file. Then I use WinDiff, a file compare
utility, to compare the versions. If you don't have WinDiff, you could use
Word for this purpose.
 
T

Tim

why not simply put comments into your code, eg: -

' Version 2.1 Saved 15/08/04 10:04

or at each area you've changed (as long as there aren't too many!)

alternatively, i presume this is connected to a workbook, so you could have
a before_close macro to save the current date/time (and even incremental
version number) to cells in a sheet

tim
 
K

Keith Willshaw

Poseur said:
Apparently a rudimentary environment like the VBE does not have
any way to track changes to modules nor can I find any plug-in
or add-on to do it.
Anyone have a system worked out?
I'm constantly changed and tweaking my projects and I do it at
home and at work so I send my files back and forth and I'm
constantly getting confused about which is which version or
latest good revision.
Click to expand...

I use Rob Boveys code cleaner to export the forms and
modules and store them in a code management system

http://www.appspro.com/Utilities/Utilities.htm

We have historically used source safe but are switching to
CVS/WinCVS

This is freeware

http://www.cvsnt.com/cvspro/

Keith
 
Top