Bug report #8360

Updated by Regis Haubourg over 6 years ago

Reading MS access datasources via ODBC, table that contain special encoded characters are not imported, and raise a error message "invalid datasource".

When dealing with encoding options, field names and content with encoded characters can be correcly imported. TIt looks like encoding options are not used for table name.



Tested with mdb and accdb databases. ODBC DSN created on windows 7 64 bits, using mdb-accdb odbc drivers 14.00.6015.1000 and mdb 6.01.7601.17632.



see attached small databases for test purposes.

Back