Description: If you try to edit an MS Access table using LO Base and an ODBC connection you get an error message saying the the bookmark is invalid. Steps to Reproduce: Use LO Base to connect via ODBC to an MS Access .accdb file using the Microsoft Access Driver version 16.000.15028.20050 ACEODBC.DLL Edit a record and then move off the record to commit the edit. Please watch this YouTube video: https://youtu.be/M_hqZegXcXM Actual Results: Error message blocking the edit of the record Expected Results: Record is edited Reproducible: Always User Profile Reset: Yes Additional Info: Please watch this video to see how to reproduce the bug: https://youtu.be/M_hqZegXcXM
Created attachment 179306 [details] Error message when editing an MS Access record using LO Base via ODBC
Have no Access and Windows here, but are you sure it is a bug of Base? I have searched for 'Access "not a valid bookmark"' and get many results. Some try to repair the database through ODBC-GUI, some says the file is corrupted …
MS Access ODBC driver is a very solid drive and I suspect it is a bug in Base. This is not a corruption issue with the MS Access database. This bug I believe is related to the other bug I filed: https://bugs.documentfoundation.org/show_bug.cgi?id=148343 You can replicate bug 148343 with Ubuntu. No need for Windows.
I confirm with 64-bit LO 7.4+ in 64 Win 7 with 64-bit Access Database Engine 2016. Should also be tested with 32-bit. Problem is that ODBC has this error and MS Access driver read-only bug 43187 so not usable at all.
Problem didn't exist with 32-bit Access Database Engine and LO. I set High because now 64-bit is usually used and users may not even think of 32/64 issue. Also because this shouldn't be a large problem. And because direct access also doesn't work so Access database not usable but relatively frequent.
Dear Claude von Roesgen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug still exists in 24.2.2