Question

use comma instead of point

  • 8 September 2020
  • 8 replies
  • 92 views

Userlevel 2
Badge +3

Hi,

for the entire app we use a lot of fields with values with a comma. However, TW by defaults uses a point. 

Now this is not too bad for our friends in the us of a. But here in Europe, I would very much like to offer a comma in values. 

Is this possible? 

It is needed for money, size, weight, etc. 

 


8 replies

Userlevel 7
Badge +14

Hi,

For that you can make use of the Domain control 'Numeric (thousands separator)’. This will cause the dot to be a comma. Only if the number is > 1000, then it will be 1.000,00 for example.

*This does make it so the field(s) will always use a comma over a dot.

Hope this answers your question!,

Mark Jongeling

Userlevel 2
Badge +3

thnx for superquick reply. 

I set the Domain to Numeric, with 10/2 as length. The control with 'Numeric?thousand separator’ 

and look: 

The exact opposite of what I want:) 

 

Secondly, can this be set somehow per user? For our app is used both in EU and US. And we would like to accommodate all. 

thnx!  

Userlevel 7
Badge +14

It might be dependent on your WIndows settings. If you use US dates in Windows, the GUI will use that too. And it could means that due to that your numbers are the American way.

There's an Extended property called UseWindowsCulture (https://docs.thinkwisesoftware.com/docs/sf/extended_properties.html) which 'Uses the region and language settings of the operating system (Windows) for displaying and editing values instead of the settings derived from the application language ID from the meta source. (Dates, times, numbers etc.)’

Maybe that is turned off. You can try out turning it On and see what happens :wink:

Userlevel 2
Badge +3

I've tried with both Yes/No settings in the UseWindows and with several pc's. Also on web gui and local app. However, still the opposite of what I want. Weird… 

Another though on this? 

Note: Date settings are picked up and correct: DD:MM:YYYY 

Userlevel 7
Badge +14

Maybe this could be an answer:

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_word-mso_win10-mso_365hp/changing-decimal-separator-from-comma-to-dot/953556fb-00d0-45ad-bd4f-6ca8afa5025a

Windows 10

In Windows the separator can be changed. Let me know if this does the trick!

Userlevel 2
Badge +3

Everday day we learn. Never knew this could be set. 

BUT! For my local app it was set correct, but does not effect in the local app. So, no changes. 

 

Userlevel 7
Badge +14

For extra context, what datatype does your field(s) have and (if they do) what domain control are you using? 

Userlevel 2
Badge +3

the domain on the field I'm testing now is: 

  • Data type; Numeric 
  • Length: 15 - 2 
  • Database type: numeric(15, 2)
  • Control: Numeric (thousands separator)

Reply