>>OK. Then he has quite a job to do, if he is not able to modify the application. I guess he has to do what I had to do 8-10 years ago, namely modify the Windows keyboard description file, and let that file be 'active' when he runs his application. The keyboard description file is basically a file which intercepts the scan codes from the keyboard and replaces each scan code with 'code' which windows 'understands'.
>
>Do you have more details on how this file can be edited.. Or where he can find it.. Or new tracks ??

Sorry. I don't think you even can, as I wrote in the next paragraph. Windows performs some CRC testing or something to verify that the files are not changed. If you change the files, you must reboot for Windows to reread them, and then Windows will 'repair' the 'damaged' files.

>>
>>That was (and still is, AFAIK) the only way to get windows to accept the decimal point on the numeric keyboard as a point (.) and not a komma (,) which oddly enough is the standard in many countries, including Norway. Extremely frustrating, to say the least, when VFP only accepts decimal point, and not decimal komma in the IDE. Since I am not able to modify these files anymore, because newer Windows believe the files are 'hacked', I now have to adjust to Microsoft's opinion about the world, and if I am not awake, I make many errors. I hope Microsoft will eventually ubderstand that this is a VERY big problem for us programmers who live where decimal komma is standard.
>
>Here in brazil comma is the standard.. But we can chage it (since VFP3) by the configurations of control panel just using the command..
>
The SET SYSFORMAT ON is fine in many cases, but not always. But I have learnt to live with it, so if they fix it I probably will nake even more errors. :-)

>

>set SYSFORMATS ON
>

>
>CLaudio