Log time spent on each record

  • Thread starter Thread starter Guy Kerr
  • Start date Start date
G

Guy Kerr

I have a customer database which our employees use to contact customers. We
contact customers on behalf of other companies and as such are open to being
audited to make sure we're following protocol. Our latest audit exposed the
fact we have no way of knowing how long we are spending on each customer.

We're looking for a way to log how long our agents are "on" a record in the
database. I was thinking of using the On Timer event to initially write a
record (then update the same record when the timer hits again) to the logging
table every 10 seconds or so I can see how long the record was active. This
doesn't seem like a very clean solution so I thought I'd ask some advice
first.

I was looking at the the other Events but wasn't sure which would be best.

Any advice would be much appreciated.

Guy
 
Guy Kerr said:
I have a customer database which our employees use to contact customers. We
contact customers on behalf of other companies and as such are open to being
audited to make sure we're following protocol. Our latest audit exposed the
fact we have no way of knowing how long we are spending on each customer.

We're looking for a way to log how long our agents are "on" a record in the
database. I was thinking of using the On Timer event to initially write a
record (then update the same record when the timer hits again) to the logging
table every 10 seconds or so I can see how long the record was active. This
doesn't seem like a very clean solution so I thought I'd ask some advice
first.

I was looking at the the other Events but wasn't sure which would be best.

Form close event.

Tony
 
It depends on the design of your form, but you might keep track of the time
they start by noting it in the form's Current event. When it fires again (or
the form closes) means they've moved to another customer.
 
Douglas J. Steele said:
It depends on the design of your form, but you might keep track of the time
they start by noting it in the form's Current event. When it fires again (or
the form closes) means they've moved to another customer.

Hmm, yes, my solution assumes that they are using a continuous form
with some filtering on top and then opening a details form where they
can do some updates.

Tony
 
Back
Top