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
Thanks a lot