Re: NLS_LANG / Two clients on the same PC with different charset

Hi Vik!

Thanks for writing. My problem is on the PC (NT) side not on the server side.

The NLS character set conversion works like this:

Oracle inserts the client data into the DB after mapping it from the client charset into the DB base charset (the character set you used when you created the database). In case of the omnis client the MAC8ROMAN8 should be mapped to ISO8859P1 (this is the code set on the server). There is an entry in the registry which tells oracle what charset is used by the clients (which is MAC in case of omnis), but there is only one. If you launch excel this uses ISO8859P1, so the mapping screws up the data.

B

In article <35606794.BD7B95BD_at_pop.gate.net>,   vgoel_at_3implant.com wrote:
>
> This is a multi-part message in MIME format.
> --------------04B2B915970B3D7F4F21125E
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Bela,
>
> Set the NLS_LANG parameters of each Oracle RDBMS in the init<sid_name>.ora
file.
>
> Hope this helps,
>
> Vik. Goel
>
> bvizy_at_oxmol.com wrote:
>
> > Dear Readers!
> >
> > I have two oracle client programs on my NT with different character sets.
The
> > first is an Omnis based application, with MAC 8 bit charset, the other is
> > plain ISO8859P1 (Excel). Is there any way to set the NLS_LANG in the
registry
> > that both data conversion work? Is there a trick to set NLS_LANG based on
the
> > client?

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Mon May 18 1998 - 16:43:04 CDT