kvilimas
asked on
wrong national (Norwegian) characters when importing dbf files into MS SQL Server
Hi,
I have tried to buid an SSIS package importing dbf files into MS SQL server database. I have problems with national characters. I use ADO Net data source with ODBC connector, I have defined DSN with uses Microsoft dbase driver. The resulting tables contain wrong charactes instead of national ones (Ø, Æ, Å). I have tried also FoxPro Ole DB driver. This one allows to force coding table ( which appears to be 1252) and results are correct, but it takes ages! to read files. I have also tried to read into MS Access 2010 database, errors are the same. The same errors when trying to open in excel.
I attach sample file.
PKPOLIKL.dbf.zip
I have tried to buid an SSIS package importing dbf files into MS SQL server database. I have problems with national characters. I use ADO Net data source with ODBC connector, I have defined DSN with uses Microsoft dbase driver. The resulting tables contain wrong charactes instead of national ones (Ø, Æ, Å). I have tried also FoxPro Ole DB driver. This one allows to force coding table ( which appears to be 1252) and results are correct, but it takes ages! to read files. I have also tried to read into MS Access 2010 database, errors are the same. The same errors when trying to open in excel.
I attach sample file.
PKPOLIKL.dbf.zip
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've never tried to import DBF files directly to SQL, you can try.
If you link or import file to Access and then import from Access to SQL, all will be OK.
If you link or import file to Access and then import from Access to SQL, all will be OK.
Before Access 2007 this parameter was in Jet path of registry:
[HKEY_LOCAL_MACHINE\SOFTWA
"DataCodePage"="ANSI"
May be it will work for SQL.
You can try to search in registry "Xbase" and "DataCodePage". By default there is "OEM"
[HKEY_LOCAL_MACHINE\SOFTWA
"DataCodePage"="ANSI"
May be it will work for SQL.
You can try to search in registry "Xbase" and "DataCodePage". By default there is "OEM"
Thank you for sharing this usefull information. One remark: changing "DataCodePage" to "ANSI" solves the problem for opening DBF files in Access 2010. Not in Excel 2010.
Is there a similar registry setting for Excel?
Many thanks.
Bbase
Is there a similar registry setting for Excel?
Many thanks.
Bbase
Sorry Bbase, as I know Excel can work only with OEM DBFs.
ASKER