Skip to content


COmmas not interpreted correctly

Dominic asked 5 years ago
I have a client who’s using Smartconnect from 2 different Terminal servers with two different Windows version, but they are using smartconnect on each TS that points to the same SQL server.  We’re constantly having issues with regional settings where on some computers, integration works fine while on other computers commas are not interpreted correctly.  so an amount of 14,76$ in excel results in a 1476$ entry in GP.
Is there a way to circumvent this?  some vb code that could convert, cast or whatever function that would format the data properly no matter where the integration is ran from? 
Dominic replied 5 years ago

Or if Smartconnect works only with a specific regional setting it would be nice to know which one.

If you would like to submit an answer or comment, please sign in to the eOne portal.