Description: The order of the columns is correct after copying from a Access (.mdb) database to a table. But the headers do not match the columns. Steps to Reproduce: 1.Open the .mdb in Base and then a Table 2.Mark the whole table, then Copy 3.Paste in Calc Actual Results: Header5,Header8,Header1,Header7,Header6,Header3,Header4,Header2 Column1,Column2,Column3,Column4,Column5,Column6,Column7,Column8 Expected Results: Header1,Header2,Header3,Header4,Header5,Header6,Header7,Header8 Column1,Column2,Column3,Column4,Column5,Column6,Column7,Column8 Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0
Please attach a minimal sample file to test.
Created attachment 140037 [details] sample files For the sample test i took the table "Artikelliste"
Needs SDBC data provider to test, so I am unable to.
@Franz : the problem we have with trying to reproduce this bug report is that this is dependent on someone in QA having : - 32 bit Win OS or 64bit Win OS running a 32bit version of LibreOffice ; and - a 32bit installation of MSOffice that includes Access. I'm afraid that there simply aren't many of us around (if any, currently) with such a setup. The result is that this bug will probably never be confirmed, especially given that the current advice for users of 32bit-MDB files that were written with an old 32bit version of Access (Access97 and earlier) is to migrate that DB to a different database format), for example using UCanAccess (http://ucanaccess.sourceforge.net/site.html).
See also: https://askubuntu.com/questions/187389/is-it-possible-to-open-an-access-2010-database-file-without-using-wine-or-virtua/519571#519571
I tried to test the MDB file with UCanAccess 4.04 - unfortunately, it fails on attempting to connect to the MDB file with an "unsupported decoding" error: "UCAExc:::4.0.4 Decoding not supported. Please choose a CodecProvider which supports reading the current database encoding." From the UCanAccess discussion forum, this appears to be linked to the incompatible use of certain query functions within Access that are not supported by UCanAccess, so I'm afraid it would appear that your only hope of being able to continue to use the MDB file is to migrate it via the most recent 32bit version of Access available and saving it in a more recent Acess format (such as accdb), then using 32bit ODBC to convert it to a different DB format.