G
Gary J. Dikkema
And then have a pop-up say... All Done! or some such thing?
Stupid question I know.
Gary D
Stupid question I know.
Gary D
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Not sure where to post this... how do you lock the screen after the user pushes a key...
J
John Vinson
And then have a pop-up say... All Done! or some such thing?
After WHAT is all done?
Context, please! What are you doing, how can Access tell whether
you're done or not, why would you WANT to lock up a user's computer (a
gross violation of Windows standards)?
John W. Vinson[MVP]
G
Gary J. Dikkema
OK John, take it easy.
I don't want to lock down the complete system...I only want to prevent
Access from accepting any keystrokes while scripts/queries/macros etc run.
I have been asked to have a popup appear AFTER macros/queries etc are
complete... perhaps something pushed to the Status line saying... action
complete or something is what is needed.
Ideas?
TIA.
I don't want to lock down the complete system...I only want to prevent
Access from accepting any keystrokes while scripts/queries/macros etc run.
I have been asked to have a popup appear AFTER macros/queries etc are
complete... perhaps something pushed to the Status line saying... action
complete or something is what is needed.
Ideas?
TIA.
M
mnature
People usually only start to pound on the keyboard when they aren't sure if
the computer is doing something, or has just hung up. You could try putting
up a message at the beginning of the script/query/macro, stating that the
database is working on something (and say that it could take up to five
minutes), and then a message at the end, saying that the database is finished
working. This could reassure the users that something is actually happening.
Sometimes a little information can go a long way towards achieving postive
results. Besides, if you tell them that it could take five minutes, and then
it takes 20 seconds, it makes them think that their machine must be really
good.
the computer is doing something, or has just hung up. You could try putting
up a message at the beginning of the script/query/macro, stating that the
database is working on something (and say that it could take up to five
minutes), and then a message at the end, saying that the database is finished
working. This could reassure the users that something is actually happening.
Sometimes a little information can go a long way towards achieving postive
results. Besides, if you tell them that it could take five minutes, and then
it takes 20 seconds, it makes them think that their machine must be really
good.
G
Gary J. Dikkema
Good idea.
The thing is some will want it some won't. Some will be annoyed at having to
acknowledge the pop-up. How hard is it to put something in the Status line?
It's not slowness that is the issue... it's some blazingly fast macros and
not being sure they have completed that is the issue here.
TIA.
The thing is some will want it some won't. Some will be annoyed at having to
acknowledge the pop-up. How hard is it to put something in the Status line?
It's not slowness that is the issue... it's some blazingly fast macros and
not being sure they have completed that is the issue here.
TIA.