Created attachment 167337 [details] broken database file STR (1) Optionally download attached example_odbc.odb and skip to step 8. (2) Run soffice with command-line parameter --base. Program presents database wizard step "Select database". (3) Click radio button "Connect to an existing database" and in the dropdown list click ODBC. Click button <Next>. Program presents database wizard step "Set up ODBC connection". (4) In "Name of the ODBC data source on your system" type "nonexistent". Click button <Next>. Program presents database wizard step "Set up user authentication". (5) Click <Next>. (6) Click radio button "No, do not register ..."; uncheck "Open the database ..."; click button <Finish>. Program presents dialog "Save as". (7) Save the database as example_odbc. Program closes. (8) Open example_odbc.odb. Program displays main database window. (9) In pane Database, click <Tables>. Observed: Program displays msgbox The connection to the data source "example_odbc" could not be establised. [unixODBC][Driver Manager]Data source name not found, and no default driver specified /home/terry/lo_hacking/git/libo6/connectivity/source/drivers/odbc/OTools.cxx:357 Expected : The message should name "nonexistent" as the data source. I observed this in a local build of commit 38b1497d (2020-11-04) built and running on debian-buster.
You are right. The messages, which appears, shows the name of the database file, not the name of the database source. Confirming with LO 7.0.3.1, but it would be a very old bug. Note: Internal databases should show the name of the database file, because the database in the file is almost "hsqldb" or "firebird". External databases should show the name of the database.
Dear Terrence Enger, 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
I still see the problem in my dbgutil of LibreOffice Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bfa25258d21430560584e3265cdd4629ee47a1b8 CPU threads: 8; OS: Linux 6.3; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Calc: threaded built and running of debian-sid.