If I open a database (.odb), then first Forms (in the left column “Database”) is marked. Just as I try to open the table of my database through marking “Tables” in the left column, nothing happens and the Database Wizard resp. LibreOffice Base froze. The error message is: “The connection to the data source "XXX" could not be established. The connection could not be created. May be the necessary data provider is not installed.” In the error details (there are two – identic to the two sentences of the error message) you find additional this information in #2: SQL Status: HY000 I need a restart (Windows) to be able to open LibreOffice again. In Version 4.3.7.2 this bug does not happen.
Created attachment 128002 [details] personal database of me
OK, so what you "forgot" to mention is that your ODB file links to an Access mdb file (Buecher/mdb). For that to work on a 64bit version of LibreOffice you need the 64bit version of the Microsoft Data Access Component, unless you were previously accessing the file via ODBC (which you don't say). Please provide complete details of the setup you were using to gain access to the mdb file, including any drivers used (Jet, DAC, ODBC, etc). Setting to NEEDINFO, please set back to UNCONFIRMED once you have provided the required information.
The reported behaviour is similar to bug 97395, possible DUP.
The pb is LO doesn't find Buecher.mdb In your case, if you put Buecher.odb in: c:\temp\database, you must have Buecher.mdb in c:\temp Indeed, unzipping your odb file and reading content.xml, I found this: <db:file-based-database xlink:href="../Buecher.mdb/" db:media-type="application/msaccess" db:extension="mdb"/> Could you check and give a feedback?
Ok, Alex and Julian, first thank you for your comments Second: I apologize for to „›forgot‹ to mention is that [my] ODB file links to an Access mdb file (Buecher/mdb).“ The thing is: I did not come to the idea, that Access could have to do something with it. In my operation system (Win 10 Pro 64), LO-Writer (4.3.7.2) has no problems to open the „Buecher.odb“. With deinstalling LO-Writer 4.3.7.2 and installing version 5.2.2.2 (x64) the problems started. This is my first bug-report in life, so I did not see any relation to the mdb (Access). Now I have deinstalled version 5.2.2.2 and reinstalled version 4.3.7.2. But in my OracleBox I have installed another Win 10 („Enterprise Evaluation“, 64bit) and installed here again the 5.2.2.2 (x64) version of LO. The problems remain, also I created in C:\ a temp-folder (and below a database-folder), where I copied the files like Julian said. In my real desktop (Win 10 Pro 64, LO 4.7.3.2) I create a odb-file like this (and there is no problem): I take „Connect to an existing database“ and select in the Pulldownmenu „Microsoft Access“ (not 2007). I go – for example – to „Buecher.mdb“, confirm („Finish“) and then I could save a new database. In my OracleBox (Win 10 Enterprise 64, LO 5.2.2.2) this happens: I take „Connect to an existing database“ and select in the Pulldownmenu „Microsoft Access“ (not 2007). I go – for example – to „Buecher.mdb“, confirm („Finish“) and then I could save a new database, what I’m doing. But then the database wizard opens and this error message arises: „The connection to the data source "New Database" could not be established. The connection could not be created. May be the necessary data provider is not installed.“ (SQL Status: HY000) After this, LO does not froze at least and I could exit LO. But if I mark „Tables“ left then the first error description goes on (frozing). Note: In my real desktop no MS-Access is installed. I have another OracleBox with (good old) WinXP, where Access 2.0 (16bit, 1994) is installed. Here I change my tables. In my real desktop I only look at the tables through LO Base. Another note: I installed Java 64 too besides Java 32 (like in „bug 97395“ is recommended) but that didn’t help.
As you have seen, if you install LO 64 bits you must have Java 64 bits. But to be sure LO may find it, rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try. Indeed, renaming the LO directory profile forces LO to rescan all the env. Give a try on your real desktop to be sure there no side effect with Oracle box.
Julian, I deinstalled Java 32 and 64 absolutely (I know, how to do it) and reinstalled only Java 64, so that no doubt could be over the „right“ java installation. After installing I controlled Tools\Options\Advanced\Java Options and the JRE was „already installed“. – But the fault remained. (The LO directory profile is at the right place, and there was no need to change.) That all went under my VirtualBox. I can understand your tip to exclude all possibilities of faults, but I’m very sure, that there will be no difference, if I do the same under the real desktop. I have made a CleanInstall last week, so I would like to hold on the „clean“ situation of my desktop. „A try on [my] real desktop“ would require a deinstallation of LO 4.7.3.2 and Java 32 and then an installation of LO 5.2.2.2 and Java 64. Again: I’m sure, that this action would not change something.
If you don't even try to rename your LO directory because you're sure there won't be any diff, I can't help here. (uncc myself of this bugtracker)
Julian, don’t get mad with me. If it is indispensable to change the LO directory, I will do it. (And I will also reinstall LO and java on my „real desktop“.) I will try also another idea: I install not the x64-version of LO but the newest x32-version (5.2.3.1) to see if the error occur here also or not.
Created attachment 128017 [details] Access-database Another idea: I add my Access-database (Buecher.mdb) here. Perhaps someone has the same errors like me.
A (little) result: I installed the brand new LO 5.2.3.1 (x32) in a new Windows 8.1 Pro 64 (over OracleBox – here you can find all ready Win-virtual-machines – *.ova – from Microsoft, your heart desires: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/#downloads). The import of my Access-database went without any problems, crashes… But the best at the end: I did not install java 32 (or 64) and it functioned nevertheless.
After trying all different cases (in all possible variations) I come to this result: With LO 5.2.3.1(x64) – no matter if java 32 or java 64 or both java is/are installed – the import of an Access database doesn’t work, also if I open a ODB file which links to an Access mdb file LO froze. With LO 5.2.3.1(x32) – no matter if java 32 or java 64 or both java or absolutely none java is/are installed – the import of an Access database works finely, also if I open a ODB file which links to an Access mdb file LO works without any problems. It seems (for me) that here’s a real bug in the x64-version of LO 5.x.x.x.
*** This bug has been marked as a duplicate of bug 97395 ***