Mr Browne's audit trail

[JohnE]

I have a request from the boss to track the users movement on the A2003 app.
I was thinking of using Allen Browne's audit trail since I've used before and
it works great. But now, rather then tracking the controls and the info
going in or changing, it is the button activity that is needed. So every
form and every button on each form would be tracked.

Can Mr Browne's audit trail be modified to accomplish such an objective? If
so, how and what would need to be modified/changed? I am a newbie to the
programming field so I'll need some guidance on this.

Thank you.
john

 

[Allen Browne]

No: logging button activity would be different.

Not too difficult to do though.

1. Create a table, with fields such as this:
ID AutoNum
DocName Text name of the form where this button is
CtlName Text name of the button
ClickTime Date/Time when the button was clicked.

2. Create a function that will Execute an append query statement to add a
insert a record into the logging table. The declaration in a standard module
will be like this:
Public Function LogClick(strForm as string, strCtl As String)

3. Add a line to the Click event procedure of each button you wish to log.
If the button is named cmdPrint, you would use:
Call LogClick(Me.Name, "cmdPrint")

 

[Dale Fye]

Allen,

You think "Click" event, rather than "GotFocus"? I know some controls
(labels, ...) don't contain "GotFocus" events, but the Click event won't fire
if you tab through a control, will it?

John,

Seems like a lot (I guess it depends on the number of forms and controls) of
work. Is the boss trying to assess what aspects of the application are being
used most? Or is he just a busy body?

--
Dale

email address is invalid
Please reply to newsgroup only.

 

[Allen Browne]

Your original post said:
it is the button activity that is needed. So every
form and every button on each form would be tracked.

Button activity = click event in most cases.

(I assume you are logging when the button was used, not every time somebody
tabbed to it.)

 

[Dale Fye]

Allen, I'm not the original OP.

I read his post and made an assumption that it was more than just buttons,
but on rereading, my guess is that your interpretation is correct.

--
HTH
Dale

Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

 

[Dale Fye]

"interloper"? I don't think I've ever been called an Interloper before.

;-)

 

[JohnE]

Okay, lets all take a deep breath and relax a bit. The purpose of this is
track the usage of the buttons on the forms. There have been changes made
and enhancements made to the Access 2003 app but now there is a question of
just who is using these and how often the new updates are used. You all
probably have had a request from some users that say the change/update is
crucial and push it to the top of the list only to find out later the users
aren't using it or if they are its very little. Also there is speculation
that some of the buttons are no longer used but we have no way of finding out
if they are or aren't. So the need for the usage tracking.
John

 

[Allen Browne]

That makes sense, John. I explained how to log your button: hopefully you
will be able to make sense of that.

Dale jumped in to add a comment, and I replied without noticing it was a
different person. Linq jumped in to help me realise my mistake. That's part
of the fun of a public forum - it's like a conversation in a public place.

NEway, I hope you can follow my logging suggestion.

 

[JohnE]

Yes I should be able to follow. Actually started looking it over today.
Thanks for the info. If I hit a sticking point I will post back to the group.
Thanks again.
John