>HKEY_CURRENT_USER\Control Panel\International > >There's a good registry class in the UT's download section that provides >all necessary methods to deal with the registry from VFP (in an elegant >mode :)). > >As for many other registry settings, the corresponding registry records may >not be found if the default value was not change. This sounds quite good - if the default has not changed, just keep it, since the Windows and VFP defaults are the same. I've dealt with this by keeping an environment variable stating the language used, and the corresponding keyboard and codepage simply follow, and depending on the value of this variable I've set the point, separator, date format etc in the app init - so it doesn't have to be done for every report. If you have a decimal comma and a period for thousands separator, and use an European keyboard, it already has a decimal comma in the keyboard driver, and all the decimal separators appear as commas in forms, reports, even in str() function. What may get wrong is if the user switches keyboard layout during data entry - but that may be dealt with in the textboxes with numeric ControlSource by simply discarding the set("separator") character and stuffing the proper set("point") into the keyboard buffer in the KeyPress event code.