"Reserved error (-7748); there is no message for this error" with MS Access on UTF8 DBs [ODBC156]
firebird-automations opened this issue · 11 comments
Submitted by: Bjoern Reimer (bnreimer)
Attachments:
odbc-156.sql
DBUTF8.ZIP
OdbcFb.zip
- Install InterBase ODBC driver
- Install Firebird Client Only
- Create an ODBC DataSource to the attached UTF8 character set Firebird database file using 32 Bit the "ODBC Data Source Adminstrator" tool.
- Start Microsoft Access 2003 or 2010
- Create a blank new access database
- Click on "External Data" tab and select "More" dropdown, "ODBC Database"
- In the wizard, select "Machine Data Source" (or User Data Source - depends on config) tab, and pick your ODBC data source
- Select any table (I selected TLATIN2) from the list of tables presented, and press OK
You are presented with an "Microsoft Office Access" error, and the data is not imported:
"Reserved error (-7748); there is no message for this error."
Commented by: @alexpotapchenko
Attach the database example for reproducing please. I can't reproduce this problem in MS access 2003 with my UTF-8 database.
Commented by: Bjoern Reimer (bnreimer)
Try Table DB-USER
I think it hase something to do with bigger varchar-fields
Modified by: Bjoern Reimer (bnreimer)
Attachment: odbc-156.sql [ 12270 ]
Commented by: @alexpotapchenko
I can't reproduce this problem. I have attached the database which I have created by your script. Can you reproduce the issue with my database?
Modified by: @alexpotapchenko
Attachment: DBUTF8.ZIP [ 12271 ]
Commented by: Bjoern Reimer (bnreimer)
Here is the missing part of the puzzle for reproducing the bug:
CREATE DATABASE 'LOCALHOST:D:\db\UTF82.FDB'
USER 'SYSDBA' PASSWORD 'masterkey'
PAGE_SIZE 16384
DEFAULT CHARACTER SET UTF8 COLLATION UNICODE_CI_AI;
The Collation seems to be important!
Modified by: @alexpotapchenko
Attachment: OdbcFb.zip [ 12272 ]
Commented by: @alexpotapchenko
The attached fixed driver for testing
Modified by: @alexpotapchenko
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 2.0.2 [ 10465 ]
Commented by: Bjoern Reimer (bnreimer)
Fix seems to work correctly
I'm testing a little bit more tomorrow!
Thank you very much!
Modified by: @alexpotapchenko
status: Resolved [ 5 ] => Closed [ 6 ]