SalStrToNumber in TD5.2 and Windows local preferences (2005-2010)
b fondraz

SalStrToNumber in TD5.2 and Windows local preferences

Post by b fondraz » 16 Jun 2010, 22:57

 Posted by:  b fondraz 


we have encountered a problem since we have upgrated some applications
from Gupta 3.1 to 5.2, particularly with the function SalStrToNumber( ).

We use applications which read a XML stream from internet. In that
stream, the decimal separator in numbers is a point ('.').
With Gupta 3.1, SalStrToNumber( ) understands this correctly.
But with Gupta 5.2, SalStrToNumber( ) uses the local preferences of
Windows, and the decimal separator in these preferences is a comma (',').
Therefore, SalStrToNumber( ) V5.2 doesn't understand a string containing
a '.' and it always returns zero.
We wonder if that problem will occur always when using SalStrToNumber( )
in our applications.
We could possibly exchange SalStrToNumber( ) by
SalStrToNumber( VisStrSubstitute( s, ".", ","), but we find this
solution not suitable.
Unfortunately, it is not possible to change the local preferences of
Do you know how to change the behavior of Gupta regarding these local
preferences ?

Thanks a lot
Bertrand FONDRAZ

Posts: 1326
Joined: 09 Mar 2017, 05:32
Location: Hyderabad, India

SalStrToNumber in TD5.2 and Windows local preferences

Post by FRBhote » 17 Jun 2010, 15:03

 Posted by:  F R Bhote 

You need to post this in the unify technical forums if you want it to be
noticed by them.

Return to “td.development”

Who is online

Users browsing this forum: [Ccbot] and 0 guests