468,234 Members | 1,747 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,234 developers. It's quick & easy.

Export Access table into MS SQL server preserving Unicode characters?

JJ
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
Jul 20 '05 #1
1 6039
dr**********@yahoo.it (JJ) wrote in message news:<1b**************************@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
Jul 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Andrew Arace | last post: by
4 posts views Thread by Anthony Cuttitta Jr. | last post: by
6 posts views Thread by Peter Afonin | last post: by
3 posts views Thread by nologin | last post: by
reply views Thread by NPC403 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.