• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1036
  • Last Modified:

Caps Lock function suddenly reverses.

We have a workstation with Windows XP and Office 2003 that is experiencing intermittent problems with "Caps Lock". The problem appears in Excel, where the Caps Lock function suddenly reverses. At that point the user can move into Access and the function works correctly. Allthough we did not be lieve the keyboard was the problem, we have switched to another keyboard without improvement. We have checked to see if "Sticky Keys" were switched on and they were not. Is there some combination of key strokes that could reverse this? Why would it not be universal?
0
DaveIsaacs
Asked:
DaveIsaacs
  • 7
  • 5
  • 2
  • +3
4 Solutions
 
synxCommented:
I assume you're physically at the workstation when you are testing this?  This may be unrelated, but I have found with some remote desktop applications, if caps lock is turned on when you log on to another machine... it's function will be reversed.
0
 
DaveIsaacsAuthor Commented:
There is no remote application here. This usually does not appear to be present at logon. And, it is not present in all applications. For the current user it shows up in Excel, but not Access and not Outlook.
0
 
synxCommented:
Bizarre.  Is it an option to re-install Excel?  That would be my next step.
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
DaveIsaacsAuthor Commented:
We could re-install but I am hoping we will get more info. I want to see if the user sees this happen in any other programs and also check on your first suggestion about whether this condition exists the first time in Excel.
0
 
synxCommented:
If you get any additional info, post it on up.  Sounds like it's one user experiencing the issue.  I assume you experienced this issue in person at the user's workstation (vs. them just describing it over the phone)?  I'll keep my eyes peeled for an update.
0
 
phototropicCommented:
Are you sure this is not the Autocorrect function?
"...- Activate the Caps Lock key (the light turns on)
- Go in Word (or Excel or other Office component) and type toggling
case (EX.: hELLO...)
- Office Autocorrect makes the correction : Hello... and seems to turn
off the Caps Lock Key (the light is off)
- BUT... when the user keeps typing, it's ALL CAPS event though the
light is off. And it's keep working reverse until rebooted..."

Qupted from here:
 http://www.tech-archive.net/Archive/Office/microsoft.public.office.misc/2004-08/1437.html

There appears to be no solution other than the user not making the initial mistake...




0
 
phototropicCommented:
You can disable Caps Lock key using this script:

http://johnhaller.com/jh/useful_stuff/disable_caps_lock/

Good luck!!!

0
 
nobusCommented:
try repairing Excel :under help>analyse and repair...
0
 
DaveIsaacsAuthor Commented:
Well, the plot has thickened. A: I have sat at the station and seen this happen. B: It has happened at more than one station with more than one user. C: We have looked at phototropic's solution and are doing some experimentation with AutoCorrect. D: In doing some trials we came up with a new suspect. Most of what we do with Excel is work on paperwork for orders that are referenced in our Access 2003 database. We have a button on our Access form that opens the Excel file appropriate to the order we are on.
Meanwhile, somewhere or another I found a way to write code in Excel to add information to the footer. In our case, we add the order number (contained in a specific field in the spreadsheet) and revision number (contained in another field). So, when Excel opens it asks if we want to enable macros. Because I received complaints about having to deal with that each time, I added SendKeys to send "Alt e" to enable macros. There is now a suspicion that something is going on as a result of that.
0
 
nobusCommented:
seems likely, yes
0
 
synxCommented:
I'd definitely pursue the SendKeys factor...
0
 
DaveIsaacsAuthor Commented:
An update: phototropic's comments about AutoCorrect have provoked some thought by the users who have experienced the problem. At this point they are trying to monitor instances in order to gather more specifics about what they were doing when the problem bagan. I think they are also seeing that there are ways they might have caused the problem to start. We have tried changing some settings in AutoCorrect .

Meanwhile, I located this:
http://forums.devx.com/showthread.php?t=38468
Using this concept I can set the CapsLock key, not diable it. If we continue to have the problem and believe the SendKeys might trigger it, I will probably add code to turn CapsLock off.
0
 
Jim P.Commented:
Dumb thought -- can you get a digital certificate to sign your macros? That would take the Enable Macros out of the picture.
0
 
DaveIsaacsAuthor Commented:
jimpen: I am not sure we know how to do that. As I said in the beginning I have tried to find documentation on how I added the feature that inserts the info in the footer and have been unsuccessful. So I am the "dumb" one at this point.
0
 
Jim P.Commented:
Haven't done it myself either, but this should give you an idea of where to look.

About macro security
http://office.microsoft.com/en-us/excel/HP030846111033.aspx
0
 
BillDLCommented:
"I added SendKeys to send "Alt e" to enable macros. There is now a suspicion that something is going on as a result of that."

SendKeys is known to cause the problem you are having, ie. toggling various keys on and off apparently at random unless you know what's causing it:

http://support.microsoft.com/kb/179987
0
 
DaveIsaacsAuthor Commented:
Thanks to phototropic for pointing me in the direction of disabling CapsLock. Thanks to nobus and synx for encouragement to pursue the SendKeys. Thanks to BillDL for sending me to kb179987, which combined with kb177674 to provide a solution.
0
 
DaveIsaacsAuthor Commented:
The problem apparently was a result of using the SendKeys. In order to continue to use this I took the code in kb177674 and used it to find the current state of the CapsLock key before using SendKeys. After SendKeys I returned the state to the previous state. So far there are no side effects. Thanks to everyone who participated.
0
 
BillDLCommented:
Thank you Dave
0
 
synxCommented:
Glad you got it working!  That was a tricky one.
0

Featured Post

Sign your company up to try the MB 660 headset now

Take control and stay focused in noisy open office environments with the MB 660. By reducing background noise, you can revitalize your office and improve concentration.

  • 7
  • 5
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now