Link to home
Start Free TrialLog in
Avatar of Nick67
Nick67Flag for Canada

asked on

Fix the dog-screwers wagons, but good.

'Oh it takes sooooooooooooooo long to actually fill out the data into the forms, and there are so many forms to fill in!  it just takes FOREVER!'

Really.

So I want some statistics, and I have some.
I timestamp when a record gets created and then when the resulting report gets printed.
But the lollgaggers got smart, and they start the records hours/days/weeks before they actually get around to completing them.
So my stats don't tell me much.
And that needs to change

So now, I want to record when a record gets made dirty and when it gets made clean again.
It'll be interesting to see how many times they make a record dirty, and for how long it remains dirty.
The likely behavior pattern should stand out in clear relief
30 seconds -- 30 seconds -- 7 minutes of youtube and gab -- 30 seconds

We'll see who can enter what in what timeframe.
And stop all the excuses.

So,  how would YOU go about measuring and recording how long it took a user to edit a record?
ASKER CERTIFIED SOLUTION
Avatar of COACHMAN99
COACHMAN99

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Nick67

ASKER

Access 2003 is still in play, so VBA is us, and data macros are not.
Still, that may be the first reasonable justification for leaving A2003 behind that I've heard.
Avatar of COACHMAN99
COACHMAN99

You could still log open and close events and leverage the enter exit change events of each control if you need more granularity.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Nick67

ASKER

Thank you both.
Events have intervened and this is a complex task given unbound data entry forms and Access 2003.
I have continued to work on it and an article may come from my efforts.
Nick67