Changing the number format on a layout only affects how the number appears on that layout; it has no effect on the data itself. In a number field, the US version of FM will treat a comma as a non-numeric character and ignore it.

Somehow you have to change the commas to periods. One way is to change a number field to a text field, run a calculated Replace on it:

Hi

I used to create FM solutions using a French OS (Mac & PC). When I started to translate my solutions in English, I had to address the 'decimal separator' issue. In French or I should say outside North America, countries use a comma as a decimal separator. So, I must format my solutions with a period instead of a comma. Recently, I've bought a PC using Windows XP (English). I thought that would solve this issue but it is not the case. I found half of the solution. In the Number window, I checked 'General format'. The modified field worked fine. I have others fields that do calculations. Those fields cause me headache. They keep calculating the number field as if it was using a comma. I formatted those fields the same way I did with the number field. The result is simple. Instead of this result: (22.34), I got this one: (2234).

Any ideas before I start from ground zero?

One thing I still don't understand is that I run FM (English version) and I use Windows (English version). The only thing in French is my keyboard but I use it in 'English (United States)'. When I create a new database, I still end up with the comma as decimal separator. Is there a way to tell FM that the period must be used as decimal separator?

I intend to try your solution later.

Bikeman17

I haven't had to develop for any system other than North American English, but I think this is a job for the Set Use System Formats script step. On=use current system formats, Off=use formats saved with database.