Re: NumLock SOLVED ??
- From: Marshall Barton <marshbarton@xxxxxxxxxx>
- Date: Fri, 27 May 2005 12:18:07 -0500
>Marshall Barton wrote:
>> That sure sounds like the wrong way around, especially when
>> you consider that NumLock is the least of the problems with
>> SenKeys.
>
grumtac@xxxxxxxxxxxxx wrote:
>Just happened to think......
>
>"Least of the Problems"...... Is there any other issue that you know of
>other than it fiddling with Numlock and Capslock ?? That is all I ever
>saw here.... The SendKeys use in our Development has two problem areas
>with the CapsLock, But had constant problems with Numlock. Capslock
>isn't too bad, because at least you stay in the same field when you
>find out the state changed. That is unlike NumLock, where users would
>end up messing up all kinds of stuff accidentally, sometimes in
>completely different forms.
>
>I will probably focus on the code of the areas where Capslock goes
>wacky and get that fixed, but then Numlocks can do whatever they want
>now with the remap :-)
>
>This is a Access97 dev, so who knows, maybe an upgrade someday will be
>the real fix for us. We figured we would use it no more than 5
>years......
>
>If you know of some other strange thing I should watch for because of
>the SendKeys use, I would appreciate hearing it. So far the Num/Caps
>issues is all I ever saw complaints about, and the commands themselves
>are doing the job.
As Nikos tried to explain in your other thread, SendKeys can
send the key codes to the wrong program. The fundamental
issue is that SendKeys is an archaic holdover from the early
days of DOS (long before Access), before application had a
real programming capability. In that environment, there
could only be a single program active on the machine, thus,
there was no confusion about where to send the key codes.
In today's multi-tasking systems, there can be many programs
running at the same time and there is no guarantee the
active program is the one you want to receive the key codes.
Even if you tell the users not to start any other programs,
there are lots of ways that programs can start
automatically.
Bottom line is that SendKeys is just plain dangerous so if
can't avoid it, keep your eyes open for your systems
exhibiting strange behavior.
--
Marsh
MVP [MS Access]
.
- References:
- NumLock SOLVED ??
- From: grumtac
- Re: NumLock SOLVED ??
- From: Marshall Barton
- Re: NumLock SOLVED ??
- From: grumtac
- NumLock SOLVED ??
- Prev by Date: Re: User defined auto keys
- Next by Date: Code to see if a value exists in table
- Previous by thread: Re: NumLock SOLVED ??
- Next by thread: Re: NumLock SOLVED ??
- Index(es):
Relevant Pages
|
