Hello All,

Received the following question from Paul Turnberg;
-------------------------------------------------------
Q: I have a macro in a program - and every time it runs it turns on the NUM LOCK. 
 
The macro does use a sell object and sendkeys

Any idea why this would be happening?

I am a programmer.  You seem to know what you are doing, based on your reply in a 
thread, and I am at my wits end. Sorry to intrude on your time.  I will look into 
your book for sure.

Thanks
---------------------------------------------------------
A:
If this is an Outlook Macro, chances are you're experiencing a characteristic whereby 
you cannot send more than one character per "Sendkey" instruction. You may send seperate 
requests for each character, or use APIs. Refer to the following article for more 
information.

http://support.microsoft.com/kb/179987

Hope this helps.

Take Care,
Mike

P.S. - Will: The original solution does not "Fail miserably" in this "big" 100's 
of AD Accounts Environment! My environment has over 50000 users plus more objects. 
Would you really prefer to logon to each machine as you suggest or use an imaging 
solution? Not practical. The best way is to detect the Machine Type (Laptop or Desktop) 
then set the desired setting in both areas an for all future users with a Build Script. 
This is merely a different deployment method for the original solution which achieves 
the same as a Customized Default User Profile in a much more practical and dynamic 
way.






On Sunday, April 24, 2005 at 12:21 pm, Mike Jankowski wrote:

>Hi Guys,

>

>If I understand your dilemma correctly, you need to set another registry key as 
desired. 

>Here's how it works; (Unless you have 3rd Party Keyboard Software Installed)

>

>After Bootup and Before Login, Windows reads the 

>HKEY_USERS\.DEFAULT\Control Panel\Keyboard\InitialKeyboardIndicators because there 

>is no user logged on. (0=Off, 2=On)

>

>After Logon, Windows Applies the setting from

>HKEY_CURRENT_USER\Control Panel\Keyboard\InitialKeyboardIndicators (0=Off, 2=On) 

>This setting is stored independantly indside each user profile, and the state from 

>the Windows Session is saved at logoff. This means if you turn your NumLock on, 
a 

>value of 2 is written at logoff, and NumLock will be toggled on at next login.

>

>Hope this helps. 

>

>

> 

• Reply or follow-up to this message

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum