I think the problem lies right at the end. When one pushes ‘Finish’ you are asked to save the file. The only option is to save it as an .odb file (which already exists). If I select this option, and to overwrite the existing file, I am told it cannot be written. So what now?
The earlier database which worked is, as far as I know,of the same vintage. Both are .mdb files. The one that does not work was in fact created by copying the earlier one. How does one tell which version the file is?
Not sure what you are attempting. Understand I am currently testing with Linux Mint as only had short access to Win system.
Have Access2000 mdb. Copied it. Created new Base file to access copied mdb. Entered all setup info using copied mdb. On ‘Finish’ selected old odb & had it overwrite it. No Problem. Newly overwritten odb now accesses the copied mdb.
Also tried just modifying the existing odb to point to different mdb using Edit->Database->Properties... and again no problem.
BTW I don’t believe there is any easy way to tell the version just from the file. It seems you need Access or some other tools from MS. Since this is for Windows it is outside of my realm. Have tried to use Wine on Linux several times but never any success getting programs to install and run.
Tried again. I can now open the file. When I try to open tables, I get a message saying that warnings were encountered, to the extent that the user either lacks privilege or the file (whose name starts @@ end includes REFS3 - which I did not think was involved), but when I press OK, I can then open the tables, but no queries or reports are visible. I guess I can update the tables but not make use of the report which I need.
Sorry, I should have added that I have now updated LO to 5.4.5.1 x64
Also have 5.4.5.1 installed. Table warnings can be the result of many things. If you mean Access queries & reports, it has always been the case that only Tables and possibly queries (don’t know exact circumstances) are accessible. Forms and Reports originally created in Access are not. Reading back over the original question (December 2017) I see some references to REFS3. But exactly what you have and what you have done to date is sketchy. Queries, reports, which odb has what?
@chrisg Start a new question with what your current problems are. Include all the dealings & procedures you have gone through thus far. This post was actually created by someone else & has been answered.
@Ratslinger - How is it possible that this incredibly detailed “how-to” has only one (1) upvote (mine!)??? This is brilliant. It deserves a medal, not a “badge”! 
Thank you!
@dajare Thank you for the comment & support. I certainly would not use terms like ‘brilliant’ or ‘deserves a medal’ as, in fact, I discovered this product years ago when needing something for Linux. Like so many other answers presented in ANY forum, most of the questions presented have have already been answered somewhere. It simply requires a little effort (or in a couple of cases a year or two) to fit things together.
Do these instructions work for Mac OS? I do not have the option of Tools - Options and get stuck at that point.
@bammbamm401 Tools>Options menu selection on Mac is LibreOffice>Preferences. However the above is specifically for Windows 10. Have also done with Linux but personally have not tried Mac OS (no access to one). From some basic searching, it seems it should work. Here is the website → UCanAccess. There is an active discussion section there which should be able to help if needed.
When I test connection in the set up user authentication I get an error of UCAExc:::4.0.4 null. I have checked the class path and the parameters and they are both the correct paths. I know this is an old question and I hope someone see this and knows what is up in my case.
@ratslinger : Thanks for the detailed steps to set up UCanAccess connector and the LO base Advanced settings. Very precise and accurate. Worked great in MS10 x64, a MSAccess2003 MDB and with LO 5.4.5.1 (x64). Connected to 12 tables with over 100,000 records. Next step is to copy tables to new odb and see how the speed is.
I tried the above instructions which seemed to be pretty straight forward so obvioulsy I am doing something wrong.
I have UCanAccess installed at the following location;
/home/glrider/data/bin/UCanAccess/UCanAccess-5.0.1.bin
Following the instructions I have put the following as the classpath;
/home/glrider/data/bin/UCanAccess/UCanAccess-5.0.1.bin/loader/ucanload.jar. An ls confirms the existance;
glrider@glrider-linux:~$ ls -al /home/glrider/data/bin/UCanAccess/UCanAccess-5.0.1.bin/loader/ucanload.jar
-rw-rw-r-- 1 glrider glrider 3629 Jan 7 2020 /home/glrider/data/bin/UCanAccess/UCanAccess-5.0.1.bin/loader/ucanload.jar
In the Parameters field I have the following;
DUCANACCESS_HOME= /home/glrider/data/bin/UCanAccess/UCanAccess-5.0.1.bin
I got through the steps to connect with JDBC. The test class button results in driver loaded successfully, so I am thinking it is my access mdb file is the issue. Once I click finish and save to an odb, I then get the following message;
The connection to the data source fims_be5 (the number gets bumped up each time I try it) could not be established
‘org.hsqldb.persist.HsqlProperties
org.hsqldb.DatabaseURL.parseURL(java.lang.String, boolean, boolean)’ ./connectivitysource/drivers/jdbcObject.cxx:189
I could swear I saw multiple slashed in the URL when I was looking, but obviously not. I have removed the extra slashes I had in the jdbc connection field and now just have the following;
ucanaccess:/home/glrider/data/LibreBase/fims_be.mdb
In the JDBC drive class field I have ;
net.ucanaccess.jdbc.UcanloadDriver
I now get a different connection error;
The connection to the external datasource could not be established
An unknow error occurred. The driver is probably defective. ./connectivity/sourcecommontools/dbexception.cxx:143
My setup:
- menu:Tools>Options>Advanced, button [Class Path…] points to ucanload.jar
- No parameters
This is my database pointing to Microsoft’s Northwind.accdb sample database:
Northwind.odb (3.4 KB)
see Edit>Database>Properties…
Same thing. I wanted to point out the 143 error should actually have been 413.
You are running LibreOffice in a container?
Don’t think so as I don’t much about containers. I am just running it on my System 76 running Pop OS.
Yes I can open that and any other odb files I have.