This content has been marked as final. Show 2 replies
There are two things to check. The first is the NLS settings for Oracle. These will get applied between the InProcess server and hte RDBMS at the OCI layer. These should be set to reflect your regional language/territory settings. The scond is the regional settings in the control panel. Since the InProcess server is using COM to talk to VB, any native COM data types that pass data to/from the OLE layer will have the regional settings applied to them.
Be aware of your session settings.
I didnot reproduce your problem but in the past I came across simular problems by switching between databases
and their releases,
which I solved by forcing my session parameters:
ALTER SESSION SET NL_NUMERIC_CHARACTERS = 'dg'
d: standing for decimal character
g: standing for group separator.
Hopes this solves your problem (in the later releases of the manuals it is more cryptic described then in the older ones.
Marc van Nes
Shell U.K. Exploration and Production
Our team is encountering a problem related to Oracle oipxx.dll decimal separator management.
We develop using Visual Basic 6 SP 4 and several versions of Oracle Client Suite, ranging from 8.0 to 8.1.7.
The executable, under several Oracle Client versions prior to 8.1.7, uses commas (",") as decimal separator, while THE SAME program, addressing THE SAME Oracle Server, on a 8.1.7 client PC, needs a dot ("."), or whe obtain a "wrong number" error while attempting to make a record insert/update.
Do You know where or what Oracle Client and the 0040 object manages the decimal separator character?
Thanks in advance for you help and attention.