467,136 Members | 1,272 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,136 developers. It's quick & easy.

Detect Idle Time

I have a routine which checks idle time and opens a pop up screen to advise
users before shutting them down. The pop up has an option for the user to
keep the application open, in which case the timer is reset for another
period.
The problem occurs if the user is working on another application at the time
the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they can
see the message?
Or is there another (more obvious?) solution to my problem?

--
Bob Darlington
Brisbane
Nov 15 '07 #1
  • viewed: 5003
Share:
21 Replies
Could you open the MsgBox as system modal, Bob?

This works in Access 2007:

Private Sub Form_Timer()
If MsgBox("Time's up. Okay?", vbSystemModal + vbYesNo, "Quitting") =
vbYes Then
'whatever
End If
End Sub
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
>I have a routine which checks idle time and opens a pop up screen to advise
users before shutting them down. The pop up has an option for the user to
keep the application open, in which case the timer is reset for another
period.
The problem occurs if the user is working on another application at the
time the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they can
see the message?
Or is there another (more obvious?) solution to my problem?

--
Bob Darlington
Brisbane
Nov 15 '07 #2
Bob Darlington wrote:
I have a routine which checks idle time and opens a pop up screen to advise
users before shutting them down. The pop up has an option for the user to
keep the application open, in which case the timer is reset for another
period.
The problem occurs if the user is working on another application at the time
the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they can
see the message?
Or is there another (more obvious?) solution to my problem?
Probably want Access taskbar icon to flash? Check out this API:

Private Declare Function FlashWindowEx Lib "user32" (pflashwininfo As
FLASHWINFO) As Long

I'm sure someone has done some VB/VBA code with this....

--
'--------------------------
' John Mishefske
' UtterAccess Editor
' 2007 Microsoft MVP
'--------------------------
Nov 15 '07 #3
Thanks Allen,
That works fine as long as the user is at his desk. But if not, it stops the
shutdown routine from quitting.
Is there any way to close an unanswered message box?

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
Could you open the MsgBox as system modal, Bob?

This works in Access 2007:

Private Sub Form_Timer()
If MsgBox("Time's up. Okay?", vbSystemModal + vbYesNo, "Quitting") =
vbYes Then
'whatever
End If
End Sub
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
>>I have a routine which checks idle time and opens a pop up screen to
advise users before shutting them down. The pop up has an option for the
user to keep the application open, in which case the timer is reset for
another period.
The problem occurs if the user is working on another application at the
time the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they
can see the message?
Or is there another (more obvious?) solution to my problem?

--
Bob Darlington
Brisbane

Nov 15 '07 #4
Perhaps you could create your own little dialog form, and open in in dialog
mode in the Timer event of your original form:
DoCmd.OpenForm "Form1", WindowMode:=acDialog

This new form could then have a default response in its own Timer event.

There's a few more details to sort out (to do with suppressing your dialog
being opened again immediately after), but that's the basic idea.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
Thanks Allen,
That works fine as long as the user is at his desk. But if not, it stops
the shutdown routine from quitting.
Is there any way to close an unanswered message box?

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
>Could you open the MsgBox as system modal, Bob?

This works in Access 2007:

Private Sub Form_Timer()
If MsgBox("Time's up. Okay?", vbSystemModal + vbYesNo, "Quitting") =
vbYes Then
'whatever
End If
End Sub
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com. au...
>>>I have a routine which checks idle time and opens a pop up screen to
advise users before shutting them down. The pop up has an option for the
user to keep the application open, in which case the timer is reset for
another period.
The problem occurs if the user is working on another application at the
time the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they
can see the message?
Or is there another (more obvious?) solution to my problem?

--
Bob Darlington
Brisbane
Nov 15 '07 #5
Bob Darlington wrote:
>I have a routine which checks idle time and opens a pop up screen to
advise users before shutting them down. The pop up has an option for
the user to keep the application open, in which case the timer is
reset for another period.
The problem occurs if the user is working on another application at
the time the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they
can see the message?
Or is there another (more obvious?) solution to my problem?
John Mishefske wrote:
Probably want Access taskbar icon to flash? Check out this API:

Private Declare Function FlashWindowEx Lib "user32" (pflashwininfo As
FLASHWINFO) As Long

I'm sure someone has done some VB/VBA code with this....
Some additional info including input from Albert Kallal:

http://discuss.fogcreek.com/joelonso...6&ixReplies=21

--
'--------------------------
' John Mishefske
' UtterAccess Editor
' 2007 Microsoft MVP
'--------------------------
Nov 15 '07 #6
Allen.
I am using a pop up form (as opposed to a message box) but I wasn't opening
it with acDialog.
So I changed it to a dialog, but it won't pop up when another application is
in use. It still skulks unseen under everything else.
I'm considering using a sound warning with a wave file to generate an alert
that the dialog is open.

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
Perhaps you could create your own little dialog form, and open in in
dialog mode in the Timer event of your original form:
DoCmd.OpenForm "Form1", WindowMode:=acDialog

This new form could then have a default response in its own Timer event.

There's a few more details to sort out (to do with suppressing your dialog
being opened again immediately after), but that's the basic idea.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
>Thanks Allen,
That works fine as long as the user is at his desk. But if not, it stops
the shutdown routine from quitting.
Is there any way to close an unanswered message box?

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
>>Could you open the MsgBox as system modal, Bob?

This works in Access 2007:

Private Sub Form_Timer()
If MsgBox("Time's up. Okay?", vbSystemModal + vbYesNo, "Quitting") =
vbYes Then
'whatever
End If
End Sub
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com .au...
I have a routine which checks idle time and opens a pop up screen to
advise users before shutting them down. The pop up has an option for the
user to keep the application open, in which case the timer is reset for
another period.
The problem occurs if the user is working on another application at the
time the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they
can see the message?
Or is there another (more obvious?) solution to my problem?

--
Bob Darlington
Brisbane

Nov 15 '07 #7
Hmm: it worked in myt current version (Access 2007), Bob.

I did not set the form's Popup or Modal properties: just opened it acDialog.
With Access 2007 minimized to the task bar, the window poped up outside the
Access window.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
Allen.
I am using a pop up form (as opposed to a message box) but I wasn't
opening it with acDialog.
So I changed it to a dialog, but it won't pop up when another application
is in use. It still skulks unseen under everything else.
I'm considering using a sound warning with a wave file to generate an
alert that the dialog is open.

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
>Perhaps you could create your own little dialog form, and open in in
dialog mode in the Timer event of your original form:
DoCmd.OpenForm "Form1", WindowMode:=acDialog

This new form could then have a default response in its own Timer event.

There's a few more details to sort out (to do with suppressing your
dialog being opened again immediately after), but that's the basic idea.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com. au...
>>Thanks Allen,
That works fine as long as the user is at his desk. But if not, it stops
the shutdown routine from quitting.
Is there any way to close an unanswered message box?

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
Could you open the MsgBox as system modal, Bob?

This works in Access 2007:

Private Sub Form_Timer()
If MsgBox("Time's up. Okay?", vbSystemModal + vbYesNo, "Quitting") =
vbYes Then
'whatever
End If
End Sub
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.co m.au...
>I have a routine which checks idle time and opens a pop up screen to
>advise users before shutting them down. The pop up has an option for
>the user to keep the application open, in which case the timer is reset
>for another period.
The problem occurs if the user is working on another application at
the time the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they
can see the message?
Or is there another (more obvious?) solution to my problem?
>
--
Bob Darlington
Brisbane
Nov 15 '07 #8
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
Allen.
I am using a pop up form (as opposed to a message box) but I wasn't
opening it with acDialog.
So I changed it to a dialog, but it won't pop up when another application
is in use. It still skulks unseen under everything else.
I'm considering using a sound warning with a wave file to generate an
alert that the dialog is open.
That's going to make you very unpopular with your users. Can I as why you
want this functionality? Is it really necessary? There are ways to force
users out of an Access application if it's needed for maintenance purposes.
Would that suit your purposes?

Keith.
www.keithwilby.com

Nov 15 '07 #9
Keith,
I have users (using TS) who often leave their workstations without closing
the program, so that maintenance cannot be done. Some even forget that they
haven't saved an edit before leaving.
So they need to be kicked out.
But this thread is to do with making me less 'unpopular', by notifying them
in advance (if they're still at their desks) and giving them the opportunity
to continue.

--
Bob Darlington
Brisbane
"Keith Wilby" <he**@there.comwrote in message
news:47**********@glkas0286.greenlnk.net...
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
>Allen.
I am using a pop up form (as opposed to a message box) but I wasn't
opening it with acDialog.
So I changed it to a dialog, but it won't pop up when another application
is in use. It still skulks unseen under everything else.
I'm considering using a sound warning with a wave file to generate an
alert that the dialog is open.

That's going to make you very unpopular with your users. Can I as why you
want this functionality? Is it really necessary? There are ways to force
users out of an Access application if it's needed for maintenance
purposes. Would that suit your purposes?

Keith.
www.keithwilby.com

Nov 15 '07 #10
Allen.
With Access minimised to the task bar, and only the desktop visible (ie
other apps minimised as well), it works fine. But, if the user is using
another app (eg Outlook) then it doesn't appear. This is using Access 2002
in Windows XP Pro.
I have tried setting it to a pop up modal and opening with acDialog.

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
Hmm: it worked in myt current version (Access 2007), Bob.

I did not set the form's Popup or Modal properties: just opened it
acDialog. With Access 2007 minimized to the task bar, the window poped up
outside the Access window.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
>Allen.
I am using a pop up form (as opposed to a message box) but I wasn't
opening it with acDialog.
So I changed it to a dialog, but it won't pop up when another application
is in use. It still skulks unseen under everything else.
I'm considering using a sound warning with a wave file to generate an
alert that the dialog is open.

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
>>Perhaps you could create your own little dialog form, and open in in
dialog mode in the Timer event of your original form:
DoCmd.OpenForm "Form1", WindowMode:=acDialog

This new form could then have a default response in its own Timer event.

There's a few more details to sort out (to do with suppressing your
dialog being opened again immediately after), but that's the basic idea.

"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com .au...
Thanks Allen,
That works fine as long as the user is at his desk. But if not, it
stops the shutdown routine from quitting.
Is there any way to close an unanswered message box?

--
Bob Darlington
Brisbane
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...
Could you open the MsgBox as system modal, Bob?
>
This works in Access 2007:
>
Private Sub Form_Timer()
If MsgBox("Time's up. Okay?", vbSystemModal + vbYesNo, "Quitting")
= vbYes Then
'whatever
End If
End Sub
>
>
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.c om.au...
>>I have a routine which checks idle time and opens a pop up screen to
>>advise users before shutting them down. The pop up has an option for
>>the user to keep the application open, in which case the timer is
>>reset for another period.
>The problem occurs if the user is working on another application at
>the time the pop up is activated, in which case it cannot be seen.
>Is there any way to shift the focus back to my access app so that
>they can see the message?
>Or is there another (more obvious?) solution to my problem?
>>
>--
>Bob Darlington
>Brisbane

Nov 15 '07 #11
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47**********************@news.optusnet.com.au ...
Keith,
I have users (using TS) who often leave their workstations without closing
the program, so that maintenance cannot be done. Some even forget that
they haven't saved an edit before leaving.
So they need to be kicked out.
So how about considering the functionality I suggested, the ability to kick
off all users at the push of a button and to keep them out until you've
finished what you need them out for?
But this thread is to do with making me less 'unpopular', by notifying
them in advance (if they're still at their desks) and giving them the
opportunity to continue.
It was the prospect of a sound being played that I thought would make that
aspect unpopular. I don't understand why you're giving users the
opportunity to continue if you need them out. I have some code that will
achieve what I'm suggesting if you want it. You can target individual
users, individual machines, or all users and machines.

Regards,
Keith.

Nov 15 '07 #12
On Thu, 15 Nov 2007 00:24:02 -0600, John Mishefske
<jm**********@SPAMyahoo.comwrote:
>Bob Darlington wrote:
>I have a routine which checks idle time and opens a pop up screen to advise
users before shutting them down. The pop up has an option for the user to
keep the application open, in which case the timer is reset for another
period.
The problem occurs if the user is working on another application at the time
the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they can
see the message?
Or is there another (more obvious?) solution to my problem?

Probably want Access taskbar icon to flash? Check out this API:

Private Declare Function FlashWindowEx Lib "user32" (pflashwininfo As
FLASHWINFO) As Long

I'm sure someone has done some VB/VBA code with this....

http://support.microsoft.com/kb/254339
Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!
Nov 16 '07 #13
On Thu, 15 Nov 2007 15:49:28 +1000, "Bob Darlington"
<bo*@dpcmanAX.com.auwrote:
>I have a routine which checks idle time and opens a pop up screen to advise
users before shutting them down. The pop up has an option for the user to
keep the application open, in which case the timer is reset for another
period.
The problem occurs if the user is working on another application at the time
the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they can
see the message?
Or is there another (more obvious?) solution to my problem?
The (oft posted) "Kick 'em Out" routine is the most common way to do
this.

Personally, I would just call the messagebox API directly with the
MB_SYSTEMMODAL option to have the application switch to Access. This
tends to *really* annoy users however, so I doubt I'd use it anymore.
(Common in applications written by programmers who feel *their*
application is the most important application running....)

Calling the messagebox API with MB_ICONEXCLAMATION or the
MB_ICONQUESTION option (Setting?) will cause the user's application
alert sound to occur, however in TS environments, it's fairly common
for sounds not to come across, so it's use is dubious.

Just use the SetTimer API call to cause the MessageBox API to go away
automatically. It will return the default setting of the MessageBox,
so set that accordingly to what return you want to happen if the user
doesn't press anything.

In this case however, all of the above is overkill. The "kick 'em
out" routine would be the preferred method. Arvin Meyer has a copy of
it at his site: <http://www.datastrat.com/Code/KickEmOff.txt>


Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!
Nov 16 '07 #14
Chuck Grimsby wrote:
On Thu, 15 Nov 2007 00:24:02 -0600, John Mishefske
<jm**********@SPAMyahoo.comwrote:
>Bob Darlington wrote:
>>The problem occurs if the user is working on another application at the time
the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they can
see the message?
Or is there another (more obvious?) solution to my problem?
Probably want Access taskbar icon to flash? Check out this API:

Private Declare Function FlashWindowEx Lib "user32" (pflashwininfo As
FLASHWINFO) As Long

I'm sure someone has done some VB/VBA code with this....


http://support.microsoft.com/kb/254339
Thanks Chuck.

For those interested in trying this code you should note that it was
meant for VB5/VB6 but will run unaltered in Access causing the form
that this code runs in to flash.

You can change the hWnd variable assignment to use the Application
Handle instead of the Handle to the form if you want Access itself to
flash (taskbar icon flashes):

' Fill the structure:
With FWInfo
.cbSize = Len(FWInfo) ' 20
'.hWnd = Me.hWnd ' flash the form
.hWnd = Application.hWndAccessApp ' flash the app
.dwFlags = FLASHW_ALL
.uCount = 5 ' number of times to flash
.dwTimeout = 0 ' how frequently (0 = default)
End With
--
'--------------------------
' John Mishefske
' UtterAccess Editor
' 2007 Microsoft MVP
'--------------------------
Nov 16 '07 #15
Keith,
Thanks for the reply & sorry about the delay responding.
There are 2 situations. One, where I need to kick 'em out to do maintenance,
in which case they don't get the option. This one is working fine, and has
been for a number of years.
The second is where a user has been inactive and forgotten to close the app.
In this case, there is a risk that they have left unsaved edits which is
obviously not desirable. It's also a question of preserving network
resources. In this second case, I want to be able to give some sort of
warning. If they've left their desk, then they wont respond, and will be
kicked out after a number of seconds. But if they are still at their desk,
and in another application, I want to give them the chance to restart the
clock.
Hope that makes things clearer.
Does your code address this problem?

--
Bob Darlington
Brisbane
"Keith Wilby" <he**@there.comwrote in message
news:47**********@glkas0286.greenlnk.net...
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47**********************@news.optusnet.com.au ...
>Keith,
I have users (using TS) who often leave their workstations without
closing the program, so that maintenance cannot be done. Some even forget
that they haven't saved an edit before leaving.
So they need to be kicked out.

So how about considering the functionality I suggested, the ability to
kick off all users at the push of a button and to keep them out until
you've finished what you need them out for?
>But this thread is to do with making me less 'unpopular', by notifying
them in advance (if they're still at their desks) and giving them the
opportunity to continue.

It was the prospect of a sound being played that I thought would make that
aspect unpopular. I don't understand why you're giving users the
opportunity to continue if you need them out. I have some code that will
achieve what I'm suggesting if you want it. You can target individual
users, individual machines, or all users and machines.

Regards,
Keith.

Nov 20 '07 #16
On Nov 15, 9:19 pm, Chuck Grimsby <c.grim...@worldnet.att.net.invalid>
wrote:
On Thu, 15 Nov 2007 15:49:28 +1000, "Bob Darlington"
Personally, I would just call the messagebox API directly with the
MB_SYSTEMMODAL option to have the application switch to Access. This
tends to *really* annoy users however, so I doubt I'd use it anymore.
(Common in applications written by programmers who feel *their*
application is the most important application running....)
I would never knowingly buy or use an application that disrespects me
sufficiently to disturb my work with a message about idle time, or
shuts itself off.
Throughout an application development career of about twenty-five
years I have always emphasized confidence in and respect for the user
and I have never regretted doing so.

Nov 20 '07 #17
lyle <ly************@gmail.comwrote:
>I would never knowingly buy or use an application that disrespects me
sufficiently to disturb my work with a message about idle time, or
shuts itself off.
Throughout an application development career of about twenty-five
years I have always emphasized confidence in and respect for the user
and I have never regretted doing so.
However people are forgetful. Yes, we know they should cleanly exit but it simply
doesn't happen sometimes.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Nov 20 '07 #18
Lyle,
I suppose it depends on whether:
a. You need to maintain your client data file on line
b. Your clients are all 'perfect' users.
Unfortunately, all my users don't fall into that category, so I'm seeking
some options.
I've found that provided I work through this type of problem with the
clients, I don't get any agro. As long as they know what is going on.
I'm talking about a small client base do it's possible to do it this way.

--
Bob Darlington
Brisbane
"lyle" <ly************@gmail.comwrote in message
news:d7**********************************@w28g2000 hsf.googlegroups.com...
On Nov 15, 9:19 pm, Chuck Grimsby <c.grim...@worldnet.att.net.invalid>
wrote:
>On Thu, 15 Nov 2007 15:49:28 +1000, "Bob Darlington"
>Personally, I would just call the messagebox API directly with the
MB_SYSTEMMODAL option to have the application switch to Access. This
tends to *really* annoy users however, so I doubt I'd use it anymore.
(Common in applications written by programmers who feel *their*
application is the most important application running....)

I would never knowingly buy or use an application that disrespects me
sufficiently to disturb my work with a message about idle time, or
shuts itself off.
Throughout an application development career of about twenty-five
years I have always emphasized confidence in and respect for the user
and I have never regretted doing so.

Nov 20 '07 #19
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
Keith,
Thanks for the reply & sorry about the delay responding.
There are 2 situations. One, where I need to kick 'em out to do
maintenance, in which case they don't get the option. This one is working
fine, and has been for a number of years.
The second is where a user has been inactive and forgotten to close the
app. In this case, there is a risk that they have left unsaved edits which
is obviously not desirable. It's also a question of preserving network
resources. In this second case, I want to be able to give some sort of
warning. If they've left their desk, then they wont respond, and will be
kicked out after a number of seconds. But if they are still at their desk,
and in another application, I want to give them the chance to restart the
clock.
Hope that makes things clearer.
Does your code address this problem?
Hi Bob,

No it doesn't but I did used to have some code that does what you're after.
Unfortunately I discarded it years ago because I got too many complaints
from the end users. I will have a dig around to see if I can find it but
I'm not hopeful.

Regards,
Keith.

Nov 20 '07 #20
Thanks Chuck.
A Google search for 'Flash Taskbar' got a post from 'Salad' (27 Oct 2004 in
this ng) which does exactly what I wanted.
Thanks again for your help.

--
Bob Darlington
Brisbane
"Chuck Grimsby" <c.*******@worldnet.att.net.invalidwrote in message
news:ef********************************@4ax.com...
On Thu, 15 Nov 2007 00:24:02 -0600, John Mishefske
<jm**********@SPAMyahoo.comwrote:
>>Bob Darlington wrote:
>>I have a routine which checks idle time and opens a pop up screen to
advise
users before shutting them down. The pop up has an option for the user
to
keep the application open, in which case the timer is reset for another
period.
The problem occurs if the user is working on another application at the
time
the pop up is activated, in which case it cannot be seen.
Is there any way to shift the focus back to my access app so that they
can
see the message?
Or is there another (more obvious?) solution to my problem?

Probably want Access taskbar icon to flash? Check out this API:

Private Declare Function FlashWindowEx Lib "user32" (pflashwininfo As
FLASHWINFO) As Long

I'm sure someone has done some VB/VBA code with this....


http://support.microsoft.com/kb/254339
Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!

Nov 20 '07 #21
Thanks Keith.
Don't worry, I found exactly what I wanted using 'Flash Taskbar' posted to
this group in 2004.

--
Bob Darlington
Brisbane
"Keith Wilby" <he**@there.comwrote in message
news:47**********@glkas0286.greenlnk.net...
"Bob Darlington" <bo*@dpcmanAX.com.auwrote in message
news:47***********************@news.optusnet.com.a u...
>Keith,
Thanks for the reply & sorry about the delay responding.
There are 2 situations. One, where I need to kick 'em out to do
maintenance, in which case they don't get the option. This one is working
fine, and has been for a number of years.
The second is where a user has been inactive and forgotten to close the
app. In this case, there is a risk that they have left unsaved edits
which is obviously not desirable. It's also a question of preserving
network resources. In this second case, I want to be able to give some
sort of warning. If they've left their desk, then they wont respond, and
will be kicked out after a number of seconds. But if they are still at
their desk, and in another application, I want to give them the chance to
restart the clock.
Hope that makes things clearer.
Does your code address this problem?

Hi Bob,

No it doesn't but I did used to have some code that does what you're
after. Unfortunately I discarded it years ago because I got too many
complaints from the end users. I will have a dig around to see if I can
find it but I'm not hopeful.

Regards,
Keith.

Nov 20 '07 #22

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by Stephane Belzile | last post: by
2 posts views Thread by Keith Wilby | last post: by
1 post views Thread by jdph40@yahoo.com | last post: by
19 posts views Thread by Frank Rizzo | last post: by
3 posts views Thread by Law | last post: by
reply views Thread by MIke Kansky | last post: by
2 posts views Thread by RP | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.