C
Cliff Gibb
During a medium complexity project, I rolled my own logger for vba (in
my case Excel programming). It's loosely based on Log4J (very loosely)
- but it made it possible for me to easily log events within my
routines - and write the lof to an external file (which I used baretail
to watch).
It sure beats Debug.Print!
http://log4vba.everage.ca
--------------------------------------------------------------------------------------------------
The Log4VBA solution is used by the developer to log fatal errors,
warnings, and information at particular points within a procedure.
The messages generated by the logger may be written to a file and the
immediate window (the console). When the code is ready to be delivered,
the logger entries may be left within the code. The developer only
needs to modify a single setting in order to disable the logging
globally.
my case Excel programming). It's loosely based on Log4J (very loosely)
- but it made it possible for me to easily log events within my
routines - and write the lof to an external file (which I used baretail
to watch).
It sure beats Debug.Print!
http://log4vba.everage.ca
--------------------------------------------------------------------------------------------------
The Log4VBA solution is used by the developer to log fatal errors,
warnings, and information at particular points within a procedure.
The messages generated by the logger may be written to a file and the
immediate window (the console). When the code is ready to be delivered,
the logger entries may be left within the code. The developer only
needs to modify a single setting in order to disable the logging
globally.