Re: OemToChar() question

From: "Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@xxxxxxxxxxxxxxx>
Date: Thu, 28 Jul 2005 17:20:49 -0700

Carl Daniel [VC++ MVP] wrote:

> Sounds like you need to be working in Unicode.

It also sounds like your source data is probably UTF-8, not OEM, so you
should really be using MultiByteToWideChar with CP_UTF8 as the source code
page and not using OemToChar at all.

-cd

.

References:
- OemToChar() question
  - From: Jeff McKay
- Re: OemToChar() question
  - From: Carl Daniel [VC++ MVP]

Prev by Date: Re: OemToChar() question
Next by Date: Re: Virtual fodler with drive letter
Previous by thread: Re: OemToChar() question
Next by thread: Re: OemToChar() question
Index(es):
- Date
- Thread

Relevant Pages

Re: Japanese to Unicode characters
... I agree with what Bart said: it sounds like your source data is not ... >store the japanese strings as Unicode. ... >Now I want to migrate the data from the Rdb to SQLserver dB and store the ...
(microsoft.public.sqlserver.programming)
Re: Help! Unicode data types in OLAP databases
... To clarify: ... There is nothing wrong with the source data (I can see all ... special unicode charaters correctly) ... >SSAS is natively Unicode there is nothing special you ...
(microsoft.public.sqlserver.olap)
Re: UTF-8 in SQL 2000 einlesen
... Gavin Porter schrieb: ... die Codierung der Textdatei ist UTF-8. ... Unicode zu speichern. ... zwischen ANSI, OEM u. UNICODE wählen. ...
(microsoft.public.de.sqlserver)