Hi Pat, Maybe I missed it, but which 4D version are you using?
The 'Use period and comma as placeholders in numeric formats' is a compatibility setting for upgraded databases from v13 (or maybe from v12). If you don't have this pref, the db was created a newer version and the setting is default on. In old 4D versions you had to provide a number format for decimal point or comma. Eg "###,##0.00" for US and "###.##0,00" for us (I mean us, belgian ;-) But if the compatibility setting is on (or in newer database), 4D does an automatic conversion. This means you have to always use the decimal point notation format, but the resulting string will be in the OS notation. I just tested in a brand new v15 db on my OS, which is using decimal comma. $number:=12345678.99//as of v15 the decimal point is also used in the method editor; beware dates have to be written as !YYYY-MM-DD! $format:="###,###,##0.00" alert(string($number;$format)) When I run this, the alert shows: 12.345.678,99 Have you tried to set the sepator values to a fixed value in your script: vDecSep:="." vThousandSep:="," ... HTH Koen (decimal comma guy) Op 21-okt.-2016, om 11:16 heeft Pat Bensky <[email protected]> het volgende geschreven: > So the number format string seems to be correct, and the first test is > correct, but WHY are we getting all those < in the second test????? -------------------- Compass bvba Koen Van Hooreweghe Kloosterstraat 65 9910 Knesselare Belgium tel +32 495 511.653 ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
