Re: Decimal point and decimal comma

Sybrand Bakker <gooiditweg_at_sybrandb.verwijderdit.demon.nl> writes:

> Apparently one driver doesn't pick up the correct NLS settings.
> (BTW: there is no such thing as 'german' or 'american' oracle, it just
> means you have changed parameters.

The problem seems that the database administrator in the net where the application is to be deployed changed the default database settings with the last update of Oracle (old version IIRC 7.3 worked fine, new version 8.1 stopped working with VB6 for datatypes NUMBER(x,y) -- for some time i'm even not allowed adminstrative access to my database and the admin was unable to create a valid dump :().

I try to test on my development system (no contact to production database server) with a complete dump of the production database.

> Could you run select * from nls_session_parameters and check
> nls_territory and nls_numeric_characters? The territory should be

My default territory is AMERICA. I already tried to play around with NLS_LANG and

  alter session set nls_territory=germany

but no changes.

> Germany. Note: if you have a default setup, and you change the windows
> locale, this changes your NLS settings as well!

Hmmm... but it seems that with the DB dump i can reproduce the problems in the production environment even if server and client runs on the same windows xp system.

Anyway: It seems only NUMBER(x,y) makes trouble, FLOAT seems to work. I'm no database expert, so: Are there any big differences? What is the difference in space?

-- 
Stefan.