Extended ASCII Character issue

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
ahcheong
Posts: 2
Joined: Fri 17 Oct 2014 11:03

Extended ASCII Character issue

Post by ahcheong » Fri 17 Oct 2014 11:06

hi support,

I'm facing problem while inserting extended ascii character.

For e.g.
input: jØdôÊð
output: j?d???

Please advice.

Shalex
Devart Team
Posts: 8072
Joined: Thu 14 Aug 2008 12:44

Re: Extended ASCII Character issue

Post by Shalex » Thu 23 Oct 2014 14:43

Please try using the "Unicode=true;" connection string option.

If this doesn't help, please give us details about the issue you have encountered:
1) make sure that the incorrect output is caused by provider (not by some environment settings for representation)
2) send us a test project with the corresponding DDL/DML script
3) specify your connection string (roughly, without credentials)
4) the exact(xx.x) versions of your Oracle server and Oracle client
5) NLS_LANGUAGE, NLS_CHARACTERSET, and NLS_NCHAR_CHARACTERSET parameters of your Oracle server
6) NLS_LANG setting of your Oracle client (in registry)
7) regional settings of your operating system: Control Panel > Reginal and Language Options > the "Standards and formats" drop-down value, Location, and Language for non-Unicode programs
8) if possible, try using the latest (4.4.612) build of LinqConnect (does the problem persist?)

Post Reply