For the most part what I use is to simply a little spreadsheet and make
notes and comments as to what I'm doing.
However, it's not clear if you want overall project history logged over a
long period of time, or you simply need a system to track the amount of time
you going to bill a client?
In the case of billing, I use my PDA, and a custom built billing
application, but I'm not sure that's really what you're looking for.
In the case of logging code changes? I don't think of any tool that will do
this for you automatically, you simply have to put the comments in your code
every time you change something. As mentioned, you could consider using
source code control to track and log your changes now, but that will not
help for any past history.
I've pasted example code from a module right after my signature in this
post, and you can see how I make comments and notes about changes and
updates made to the code. You can have an automated system (source code
control) track what you've changed to see what you edited in the past, but
if you don't state what you've done, then how does that help you anyway?
In other words, unless a human being enters some kind of comments and notes
as to what the actual changes are, there's really no way to automate this
whole process. If you're willing to enter the date and time, and what your
changes are, then simply just open up a text document, perhaps a word
document, or often as I suggested simply an excel document and enter some
notes + date into that sheet every time you make a change.
In other words you certainly don't have to spend any money on a solution
here, and virtually anything out there would force you to enter some notes
as to what you're doing. I just think a little note pad or excel will do the
trick fine in this case.
Anyway take a look at my comments right after this signature here, and
you'll see how I log changes made to code...
Note in the following comments, those logged changes are for one single sub
that I was working on over the years.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
'******************************************
'* Word merge code *
'* (c) 2001 Albert D. Kallal *
'* (e-mail address removed) *
'* *
'******************************************
'
' Usage:
' In code on a form with a data source, just place the following
' command behind a button
'
' MergeSingleWord
'
' That is it!!!
'
' You can also specify a dir for the above. This dir location is
relative
' to location of the access dir. The default dir is "Word\". Hence, the
real
' usage is:
' MergeSingleWord [dir],[bolFullPath]
'
' Example:
' MergeSingleWord "Customers"
'
' The above would use/create the templates in a dir called Customers
(relative to app dir).
' The "\" is optional. If you leave out the "\", then my code appends a
"\" to the dir
'
' An absolute location can be specified as:
' MergeSingleWord "c:\MyWord\", True
' The use of the True above forces the dir to be a full path name, and
not relative
' to the app dir. The path must be a FULL path, and not relative.
'
'==========================================
' Revisions
' Date who Comments
' May 20, 2003 ADK - added on error resume next to the mkdir command in
GetWordDir
' May 20, 2003 ADK - changed merge.txt file to merge.888 to fix text
import bug
' (this is a know problem when you turn off file
extensions
' in windows, the mail merge will fail KB article
137385)
' Aug 06, 2003 ADK - added ability to use different dir for each form.
' Aug 09, 2003 ADK - added a listbox sort routine
' Aug 28, 2003 ADK - change the "modify" template option to *always*
set the
' data source to merge.888. That way, just hitting
modify option
' will set the data source to the correct dir.
'
' Oct 22, 2003 ADK - changed the "qu" routine that surrounds the text
data field to
' remove all " quotes to a ' (single quote).
'
' Oct 29, 2003 ADK - removed use of AppActivate "Microsoft Word" to use
' wordApp.Activate (this works with all versions,
including xp where
' the window names are "separate"
' Feb 14, 2004 ADK - Added the code to set the data source EACH TIME a
word doc is loaded.
' (This was done to fix problems with office 2003, and
the message:
' "Opening This Will Run the Following SQL Command
Message"
' There is a number of registry settings that can be
changed. However
' just setting the data source EACH TIME the word doc
is loaded also
' seems to by-pass the run SQL command nag message.
Since this is hole
' in what is supposed to prevent automation code from
setting the data
' source, I am betting that future releases will beak
my code!
' Sept 24, 2004 ADK - added some code to allow name of output doc to be
set.
' Mar 06, 2005 ADK - unbound text boxes are now included for single
word merge
' Sep 07, 2005 ADK - mergenoprompts now allows sql string to be based
' Oct 10, 2006 ADK - text boxes on forms now can be used in the merge.
' Oct 14, 2006 ADK - fill prompt fields cased menu bars to not show,
fixed by
' moving the visible + activate code to BEFORE the
merge.
' Dec 11, 2006 ADK - fixed a focus bug, and now use a SEPERATE instance
of
' the "open" word document to fix a problem when
docuemnts
' are already open
' Dec 03, 2007 ADK - changed the openreocrdset commands to use
dbSeeChanges
' (this allows the code to work un-modifed with sql
server
'
' Mar 14, 2008 ADK - made merge.888 text file *local* dir. This shold
allow
' multi-user operation.
Public Function MergeSingleWord(Optional strDir As String = "Word\", _
Optional bolFullPath As Boolean = False, _
Optional strOutPutDoc As String = "")
