Documenting Revisions

[tbeers]

Good Morning.

I am using Access 2007....Is there any way to document revisions and changes located within the program? I know there is a documenter but it is large and cumbersome and nearly useless to me for tracking changes. I suppose I could just do a spreadsheet or something.

Thanks

Tomb

[PianoMan64]

Good Morning.

I am using Access 2007....Is there any way to document revisions and changes located within the program? I know there is a documenter but it is large and cumbersome and nearly useless to me for tracking changes. I suppose I could just do a spreadsheet or something.

Thanks

Tomb

Hey Tomb,

What I've found to be most effective for myself is to create a table that you keep local to the MDB, MDE, ACCDB, or ACCDE that you list any of the changes that you perform on the application. This way you can have a list of all changes and the dates/times that they were done. This will help the next programmer that may come along behind you, if you ever depart.

Hope that helps,

Joe P.

[youmike]

Another suggestion: I use a VBA module, which I call modVersions. In it I note version numbers and dates of introduction of each of those versions and notes on what has changed. Here's an example:

Global Const gcstrModule As String = "PAR"
Global Const gcstrVersion As String = "08133"

'*** 07001 10 Sep
'*** 07002 14 Sep
'   LU_Staff corrected
'   StartUp options activated.
'*** 07003 17 Sep
'   frmWorkerlist added
'*** 07005 7 Nov
'   referencesd corrected in LU_ProdActPict
'*** 07006 8 Nov
'   LU_ProdAct corrected
'*** 07007 28 Dec
'   Correct screen added
'   numerous minor adjustments
'*** 08001 22 Jan
'   Three classes of activity added
'*** 08102 5 Feb 2008
'   08101 with tbldateParameters manipulation removed
'   08101 rewritten to allow for four types of ProdAct
'*** 08103 13 Feb
'   reporting and correction added
'*** 08104 13 Feb
'   prod hours percentage added
'*** 08105 14 Feb
'   rptTeamDateRangeSummry paper size corrected
'*** 08106 18 Feb
'   Date of entry tests relaxed
'*** 08110 8 Apr
'   Period Index spreadsheet creation added
'*** 08112 27 May
'   LU_Staff corrected
'*** 08113 1 Jul
'   references to cboProdActType corrected in frmType_all
'   Worker daily total s option added for period in people reporting
'   ProdActGroup introduced
'*** 08114 17 Jul
'   prodact types corrected in option box on capture form
'*** 08115 17 Jul
'   minor correction to capture form - ref to Me.cboProdActId was Me.cboProdActType
'*** 08116 21 Jul
'   multiple errors in period day counting corrected - was working with working days in period, not calendar days
'*** 08117 22 Aug
'   frmReportsPeople hierarchy redesigned
'   frmTeamLeaderEdit introduced
'*** 08119 18 Sep
'   Minor reporting adjustments
'*** 08120 21 Sep
'   Prod Pts added to summary report
'*** 08121 22 Sep
'   Prod points calc now uses Non-Penalty hours
'*** 08130 25 Sep
'   Pict & plant based reporting added
'*** 08131 1 Oct
'   GroupSize introduced
'*** 08134 2 Oct
'   GroupSize calculations added
'   frmReportsContainer created
'*** 08134 3 Oct

The two global constants at the top are the code to identify the database and the version number. These are global constants because they are displayed on the splash screen. The first two digits of the version number are the year. Using this approach, you can adapt it to make it work the way you want and it is pretty much hidden from users. Each version comment can be as long as short as you feel necessary.