Friday, March 23, 2012

Export Access table into MS SQL server preserving Unicode characters?

Hi,

usually, I'm not using MS servers, but I have a big problem with a
Access table.

I should create a web application for a Historical Dipartment.
They have create a populated a Access database using unicode
compression field (for ancient language).

I would like to export this table into MySQL o Postgres, but it's
impossible because when I export this table in a .txt o cvs format the
unicode charaters have been "destroyed" for memory allocation problems
(cause Access use a compression tool for unicode fields).
Also with professional tools for dump Access to another DBMS.

I would to know if using a MS SQL server I can skip this problem cause
both MSQLserver both Access are Microsoft product.

Thank you ;)
Jdreamers_spa@.yahoo.it (JJ) wrote in message news:<1b641cf1.0402030348.1ca6bdd8@.posting.google.com>...
> Hi,
> usually, I'm not using MS servers, but I have a big problem with a
> Access table.
> I should create a web application for a Historical Dipartment.
> They have create a populated a Access database using unicode
> compression field (for ancient language).
> I would like to export this table into MySQL o Postgres, but it's
> impossible because when I export this table in a .txt o cvs format the
> unicode charaters have been "destroyed" for memory allocation problems
> (cause Access use a compression tool for unicode fields).
> Also with professional tools for dump Access to another DBMS.
> I would to know if using a MS SQL server I can skip this problem cause
> both MSQLserver both Access are Microsoft product.
> Thank you ;)
> J

You could use DTS or a linked server to get the data directly into SQL
Server, provided that you define the destination columns as a Unicode
data type (e.g. nvarchar). But you might want to post this in an
Access newsgroup, as exporting data to a file with Unicode characters
intact is presumably something that has been done before (and changing
database platform to resolve an import/export issue seems a little
drastic).

Simon

No comments:

Post a Comment