Problem with Num Lock

Topic

New Reply

Access 97 – I’ve been unable to find a solution to a problem I’ve been struggling with for a while. On a form with numeric and text fields, tabbing from a numeric field to a text field turns the Num Lock off. Tabbing into a numeric field does not turn Num Lock back on.

From an end user standpoint, this is incredibly annoying since most people assume their Num Lock is always on. My original thought was that the app was corrupted somehow, or that it was an OS issue (I originally saw it on NT Workstation 4.0). However, I’ve experienced the same issue with multiple Access 97 db’s, running on different OS’s (NT, W95, W98).

I have a feeling I’m missing something terribly obvious. If anyone can point it out I’d sure appreciate it!

Reply | Quote

Replies

That sounds quite bizarre . You wouldn’t happen to have an Event in the property of the text field something along the lines of SendKeys “{Numlock”} would you ?

Reply | Quote

I’ve had the same problem when rebooting a PC the num lock was defaulting to not on. I think it was within Windows 95 but can’t be certain.

I think I got round it by sendkeys on opening the database somehow.

Reply | Quote

Num lock is usually set at the bios level – press F2, F10 or whatever key gets you into your computer set up when you first start it up. Scroll through the menus until you find something that looks like ‘Num’, and set the default to ‘On’. Save the changes, and continue with booting up.

Just be aware that messing with the setup _can_ cause problems if you don’t know what you are doing, so ask your nearest computer whiz to help if you need it.

Finally, sorry if this is stuff most people know!

kiwi44

Reply | Quote

Don’t have any SendKeys events that could cause this. I have tried using SendKeys to fix it though (turn the Num Lock on when moving to a numeric field), but it gets ignored.

Reply | Quote

Sounds very suspicious. I wonder if it’s not Access at all but some system wide problem. Can you reproduce it TABing in Word for example ? I’ve had WinDohs suddenly interpret CTRL and TAB in weird and wonderful ways but re-boot always solved the problem.

Reply | Quote

Problem with the system-wide theory is that that happens on many different computers, at different client sites, under different OS’s.

It’s also odd that the SendKeys event to turn Num Lock back on is ignored.

Reply | Quote

I think I’ve had this problem when using the > or <. This will force the text field to either all upper or all lower case depending on what you use.. This is usually set in the default value of the text field on a form or in the default value of the underlying table. If this is set try removing it.. It may solve your problem..

Reply | Quote

I ran across the solution to this on AccessWeb. They refer to a “well-known” bug with SendKeys in all versions of Access that can turn the NumLock off. I got rid of the SendKeys references I had (sloppy coding anyway), and the problem has gone away.

Reply | Quote