MS Access character set in Query
lazarus / 16-Databases

----------------------------------------------------------------------
BigSnake · 2014-05-15 06:29

When loading MS Access database I lost my national  chars.
Sometimes I get '?', sometimes words or part of them disappeared.

In ODBCConnection.CharSet I tried to use:
-EASTEUROPE_CHARSET
-Windows-1250
-UTF-8
-ISO-8859-2
but nothing happened.

Any advice?

I created small attachment to show as example.

----------------------------------------------------------------------
LacaK · 2014-05-16 10:16

TODBCConnection does not take into account CharSet property. So
setting it has no efect atm.

I do not know if MS Access ODBC driver supports supplied CharSet as 
parameter in connection string. If yes, then you must add it to
connection string.

See http://wiki.freepascal.org/ODBCConn

----------------------------------------------------------------------
BigSnake · 2014-05-21 12:05

In Params of ODBCConnestion in  I made connection string with
parameters like:

----
DBQ=base\testbase.mdb
charset=Windows-1250
---
and nothing.
I tried to use different words in parameter 'charset' and still
nothing.
Maybe parameter 'charset' is wrong, but i have no idea which is
correct.
Who know which i should use?
Any help?

----------------------------------------------------------------------
Mike.Cornflake · 2014-05-21 12:24

Had a quick google
http://www.connectionstrings.com/access/

The only slightly relevant keywords I can find there are
ExtendedAnsiSQL=1;
Or
Locale Identifier=2057;  (No idea what locale you'd need, but this may
only be date related)

Other than that - I'm not having any luck...  

You may glean some info from this forum post
http://forum.lazarus.freepascal.org/index.php?topic=20882.0

UPDATE:
Don't know if this is a general issue, but during my googling I noted
JDBC seems to have a problem with case sensitivity.  Doubt it'll be
the same on the general ODBC connection string, but try "charSet"
instead of "charset".  And over on the JDBC sites, Windows-1250 (or
other Window-XXX) never worked, but "UTF-8" seems to be the go...