Recently while using FoxPro, my numeric keypad quit working. All keys on the main keyboard, including the number keys, continued working as normal while using FoxPro.
The thing that drove me crazy for two days is that the keypad would work normally in all programs EXCEPT FOXPRO. In FP, the keypad worked as if the number lock was set to 'off', even when it was set to 'on'. And it did not matter whether I was in the command window, an editing window, or even running one of my FP applications. And the same exact applications would run normally on another system, even though the application was residing on a central server from which both machines ran the same application.
Eventually, I narrowed the problem down to the copy of FP on the one machine, but I could not find ANY settings anywhere that could be accessed which would solve the problem. So, before I reloaded a fresh copy of FP, I checked the preferences folder and found a FoxPro Settings file in that folder.
I opened the Settings file in SimpleText and found number lock was set to '0'. When I opened an older copy of the Settings file, number lock was set to '1'. So, I changed the '0' to a '1' in the latest file, saved it, and restarted FoxPro. PROBLEM SOLVED!
What I do not understand is HOW the number lock setting was changed in the first place. Neither can I find anywhere in FP where it can be set or unset either on purpose or by accident. Regardless, I am VERY happy to have the numeric keypad working properly again.
If perchance your numeric keypad quits working in FoxPro, verify that number lock in the FoxPro Settings preference file is set to '1'. If it is set to anything else, change it and see if that solves your problem. As usual, ALWAYS, ALWAYS, make a copy of the file BEFORE you make any changes just so you don't accidentally make things worse.
Using FP 2.6 on a Mac.
mmerlinn
Poor people do not hire employees. If you soak the rich, who are you going to work for?
"We've found by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding. Answering questions for careless and sloppy thinkers is not rewarding." - Eric Raymond
The thing that drove me crazy for two days is that the keypad would work normally in all programs EXCEPT FOXPRO. In FP, the keypad worked as if the number lock was set to 'off', even when it was set to 'on'. And it did not matter whether I was in the command window, an editing window, or even running one of my FP applications. And the same exact applications would run normally on another system, even though the application was residing on a central server from which both machines ran the same application.
Eventually, I narrowed the problem down to the copy of FP on the one machine, but I could not find ANY settings anywhere that could be accessed which would solve the problem. So, before I reloaded a fresh copy of FP, I checked the preferences folder and found a FoxPro Settings file in that folder.
I opened the Settings file in SimpleText and found number lock was set to '0'. When I opened an older copy of the Settings file, number lock was set to '1'. So, I changed the '0' to a '1' in the latest file, saved it, and restarted FoxPro. PROBLEM SOLVED!
What I do not understand is HOW the number lock setting was changed in the first place. Neither can I find anywhere in FP where it can be set or unset either on purpose or by accident. Regardless, I am VERY happy to have the numeric keypad working properly again.
If perchance your numeric keypad quits working in FoxPro, verify that number lock in the FoxPro Settings preference file is set to '1'. If it is set to anything else, change it and see if that solves your problem. As usual, ALWAYS, ALWAYS, make a copy of the file BEFORE you make any changes just so you don't accidentally make things worse.
Using FP 2.6 on a Mac.
mmerlinn
Poor people do not hire employees. If you soak the rich, who are you going to work for?
"We've found by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding. Answering questions for careless and sloppy thinkers is not rewarding." - Eric Raymond
