AndrewMozley
Programmer
I am running an old Clipper 5.2e application. It had been running in a cmd window under Windows XP. I now have a 32-bit Windows 7 machine and the program will still run in a Command window. My keyboard is (I believe) a standard UK Keyboard with the key on the right just to the left of the enter key and above the Shift key containing the Hash key (#) with the Tilde (~) above it.
The application has some sequences where the user can use this hash key. If I fire up the command prompt and press the hash key this correctly echoes. If however I then invoke my application I find if I press the hash key (within a standard GET sequence) it is echoing as backslash (\). This did not hapen under Windows XP, and I do not believe that I have anything in my program which changes the keyboard.
If I then exit from my program, back to the command prompt, the hash key echoes correctly.
I realise that I can persuade my users to work round this by pressing the sterling (£) sign within my application, an d that this will echo as a hash (#), but I would prefer not to have to make them change their way of working.
Grateful for any suggestions
The application has some sequences where the user can use this hash key. If I fire up the command prompt and press the hash key this correctly echoes. If however I then invoke my application I find if I press the hash key (within a standard GET sequence) it is echoing as backslash (\). This did not hapen under Windows XP, and I do not believe that I have anything in my program which changes the keyboard.
If I then exit from my program, back to the command prompt, the hash key echoes correctly.
I realise that I can persuade my users to work round this by pressing the sterling (£) sign within my application, an d that this will echo as a hash (#), but I would prefer not to have to make them change their way of working.
Grateful for any suggestions