Microsoft Access Team Blog

I have a system that I use in every DB I write that logs errors to either (or both) a table (same / different DB) or a text file (Via TextStream).  This logs DateTime,Err.Number,Err.Description,Object Source (Form Name),UserName, PC Name

I then added another module that is often used in the testing phase thats checks an error number has not already occured and if it hasnt prompts the user to explain what they were doing to cause the error (if they know) and this is also logged.

On top of this I've implement a system to capture a Screen Shot and then save this in the [App Path]\Logs\ folder.  The Path to this is also appended in the Log.

This is over the top once the project is live - so the admin person can choose the options that they want on an Err.Number basis

I would be happy to provide a simulation of how this works if you wish

A similar system is generally applied to logging of user activity - In/Out (KPI Reporting), Actions that changed data (Old/New Value on changed fields), When a Delete is perfomed Old record is added to the log then its 'deleted' from the Live Data

In my office we have several depending on what division innitiates the project.

Jira, Remedy, Magic. Bugzilla is another one that I have heard mentioned in the office, but I don't specifically get any projects from that application.

The systems I have used over the past 7 years include Request Tracker (RT), Bugzilla, Trac, TrackIT, Jira, and some php bug tracking software from 2002 or so.

The one that I enjoyed the most is the most heavy-weight one - Jira. The reasons were that it was the most customizable with the least amount of developer time required. There is a stable API that allows module writers to add additional functionality.

I haven't used many light-weight Bug Trackers as I've found that too while they make it fast, they give up too much flexibility to add new fields / change date field displays (dd/mm/YYYY vs mm/dd/YYYY), don't have a functional calendar (or ability to send reminders to calendar entries (especially expired/missed due dates)), etc.

To respond to your specific question though - I do think it is a good idea for a Bugdb template as Microsoft does have a long history of working on bugs (from almost 30 years of being in business and all) which would give you a great insight into the general needs of all sizes of development teams. I would be very interested to see what the template looks like (once developed).

We use Groove with a customized 'forms tool'

In every piece of code I use a procedure called write_2_log which I wrote.

It records in a log table simple data - user name, date-time, form the user is on, control the user has selected (usually a button), access error$ message

This identifies very quickly a procedure that is giving trouble generally and needs a good looking at

Further to first email in this post - the development stage also allows email generation to held identify bugs.

RE: Kens comment

I had an issue where the system randomly crashed - always around the same time.  The logging system was logging all errors and in the process the errors were identified as being independent of user/pc but always around the same time.

A review of the log, in conjunction with the IT guys in this 24/7 company showed that whenever the system crashed it was the same day the backup ran late - and had locked the MDB Folder out...

There are any benefits to be had for simple error handling & logging routines

I use a function that writes to an error log table in some cases.  I don't implement it everytime because of lasiness.  I do in cases when it's hard to find exactly where the error occurs such as when there are many steps in a transaction, or when a certain error is not immediately repeatable.

It would be nice is there was a way to reference the name of the calling procedure or function.  Maybe there is but I don't know how.  That way one could simply call the error logging function in any error handler and log the calling function name.  Right now I have to type the function name in as a string to log it.

I good improvement might be to add simple error handling code to the default code that is inserted when you start a procedure or function.

For example, when you type:

Function MyFunction() as boolean

'End Function' is inserted automatically.

Why not also insert the following automatically:

On Error Goto Err_Function

Exit_Function:

Exit Funtion

Err_Function:

msgbox err.description

resume exit_function

End Function

Access does this from the wizards, but not from Event properties window nor when typing in vba.

Of couse you could make it optional so oponents don't freak out.  Even better, make it configurable by having an option to specify what code gets inserted automatically in the Access or db options.

HTH,

Josh

Thanks,

Josh

I use OnTime from axosoft and it's a great tool.

Around two months ago clintc made a post asking if anyone would be interested in a light-weight bug tracking

Around two months ago clintc made a post asking if anyone would be interested in a light-weight bug tracking