I was just about to call my tech support guys and have my keyboard replaced.....but the problem seems to be a Macro with SendKeys command...
Setup:
WinNT
Access97
Situation:
I use a very specific error handling routine that traps almost every error I have ever encountered and gives general error if the specific error is not found. Instead of coding the:
On Error GoTo, et al
in all my procedures and functions, I am currently using the AutoKeys Macro with F12 mapped to a series of SendKeys commands that populates my procedure or function with my error handling data....along with some other stuff.....
What I noticed was my NumLock key seemed to "randomly" turn itself off. I was going to call the tech guys and then I noticed that when I hit the F12 key the NumLock is turned off. I don't see anything in the code that should be doing this.....Converting the code to VBA and having the AutoKeys Macro run this is no help either....Below is the macro converted to VBA for your viewing pleasure.
Any suggestions/alternate methods would be appreciated. Thanks.
========================================================
SendKeys "~", False
SendKeys "'****************************************~", False
SendKeys "'Created By: Robert L. Johnson III~", False
SendKeys "'Mod Date: xx/xx/xxxxe~", False
SendKeys "'Purpose: Enter Purpose~", False
SendKeys "'Usage: Enter Usage~", False
SendKeys "'Output: Enter Output~", False
SendKeys "'****************************************~", False
SendKeys "~", False
SendKeys "On Error GoTo MeError~", False
SendKeys "~~~", False
SendKeys "MeExit:~", False
SendKeys " Exit Sub~{BS}", False
SendKeys "~", False
SendKeys "MeError:~", False
SendKeys " Call ErrorHandler{(}Err.Number{)}~", False
SendKeys "Resume MeExit~{BS}", False
The secret to creativity is knowing how to hide your sources. - Albert Einstein
Robert L. Johnson III, A+, Network+, MCP
Access Developer/Programmer
Setup:
WinNT
Access97
Situation:
I use a very specific error handling routine that traps almost every error I have ever encountered and gives general error if the specific error is not found. Instead of coding the:
On Error GoTo, et al
in all my procedures and functions, I am currently using the AutoKeys Macro with F12 mapped to a series of SendKeys commands that populates my procedure or function with my error handling data....along with some other stuff.....
What I noticed was my NumLock key seemed to "randomly" turn itself off. I was going to call the tech guys and then I noticed that when I hit the F12 key the NumLock is turned off. I don't see anything in the code that should be doing this.....Converting the code to VBA and having the AutoKeys Macro run this is no help either....Below is the macro converted to VBA for your viewing pleasure.
Any suggestions/alternate methods would be appreciated. Thanks.
========================================================
SendKeys "~", False
SendKeys "'****************************************~", False
SendKeys "'Created By: Robert L. Johnson III~", False
SendKeys "'Mod Date: xx/xx/xxxxe~", False
SendKeys "'Purpose: Enter Purpose~", False
SendKeys "'Usage: Enter Usage~", False
SendKeys "'Output: Enter Output~", False
SendKeys "'****************************************~", False
SendKeys "~", False
SendKeys "On Error GoTo MeError~", False
SendKeys "~~~", False
SendKeys "MeExit:~", False
SendKeys " Exit Sub~{BS}", False
SendKeys "~", False
SendKeys "MeError:~", False
SendKeys " Call ErrorHandler{(}Err.Number{)}~", False
SendKeys "Resume MeExit~{BS}", False
The secret to creativity is knowing how to hide your sources. - Albert Einstein
Robert L. Johnson III, A+, Network+, MCP
Access Developer/Programmer