I'm running MS Access 2002 in a multiuser environment, and I would like to
have some VBA code that shut down a front end application if the user has
not done anything with the data or interface for a given period of time. Is
there a way to do this? I'm familiar with VBA's TimerInterval property and
Timer function, and I'm aware of the Quit method of the Application object.
Two things I don't know are:

1. how do you monitor whether the user is typing keystrokes or moving the
mouse in any way, anywhere in the application, and
2. where to put the code that does this.

The reason this is of interest to me is that I'm using the OpenRecordset
method to maintain a persistent connection with the back end to improve
performance, and sometimes a user will open a connection and go to lunch or
start working on something else before closing the connection. I would like
a way to overcome the problem of having more connections open at any time
than necessary. (Am I right in thinking that it's a good idea to keep as
few connections open as possible? Does it make any difference, if some of
them aren't doing anything with it?)

So I'm trying to eliminate situations where a user opens up a connection to
the back end, and prolongs the connection longer than necessary.

Thanks in advance,

Paul

Paul

Maybe this will help... http://support.microsoft.com/?id=128814

--
Steve Schapel, Microsoft Access MVP


Paul Ponzelli wrote:
> I'm running MS Access 2002 in a multiuser environment, and I would like to
> have some VBA code that shut down a front end application if the user has
> not done anything with the data or interface for a given period of time. Is
> there a way to do this? I'm familiar with VBA's TimerInterval property and
> Timer function, and I'm aware of the Quit method of the Application object.
> Two things I don't know are:
>
> 1. how do you monitor whether the user is typing keystrokes or moving the
> mouse in any way, anywhere in the application, and
> 2. where to put the code that does this.
>
> The reason this is of interest to me is that I'm using the OpenRecordset
> method to maintain a persistent connection with the back end to improve
> performance, and sometimes a user will open a connection and go to lunch or
> start working on something else before closing the connection. I would like
> a way to overcome the problem of having more connections open at any time
> than necessary. (Am I right in thinking that it's a good idea to keep as
> few connections open as possible? Does it make any difference, if some of
> them aren't doing anything with it?)
>
> So I'm trying to eliminate situations where a user opens up a connection to
> the back end, and prolongs the connection longer than necessary.
>
> Thanks in advance,
>
> Paul
>
>

> Maybe this will help... http://support.microsoft.com/?id=128814
> Steve Schapel, Microsoft Access MVP

That's exactly what I was looking for.

Thanks, Steve.