# Revision history [back]

Can't see how just an update to LO would affect the split DB. Been running split DB's since LO v4.3.x and currently at V5.2.3.3 and never had a problem when upgrading. Embedded DB's wouldn't be affected since the location is within LO.

With a split DB it depends upon the method the split was performed and what if anything was done afterward. There have been two (somewhat automated) methods of splitting DB. The first had no HSQL update (used v1.8 I believe) and the latter uses HSQL v2.x and also provides some portability if the macros aren't touched.

I can easily reproduce your problem (except for the inserted class paths - baffling) by moving an older type split DB to a new location. Only have to change two things to fix this. Using a BACKUP COPY (always protect yourself), open the .odb with an archive manager. Right click content.xml file and open with a text editor. Look for:

data-source-setting-value>file:THE DIRECTORY CURRENTLY POINTED TO/hsqldb.jar


and change it to the correct location of the driver directory of the .jar file. Save the change and update the file in the archive. Second, run the .odb and from the menu select Edit->Database->Properties... and make sure the directories in the Datasource URL are correct. Those two steps should fix the problem.

With a newer split DB there should not be a problem moving the DB around (I have not experienced any). However if things were somehow changed, look at the same items previously mentioned.

Can't see how just an update to LO would affect the split DB. Been running split DB's since LO v4.3.x and currently at V5.2.3.3 and never had a problem when upgrading. Embedded DB's wouldn't be affected since the location is within LO.

With a split DB it depends upon the method the split was performed and what if anything was done afterward. There have been two (somewhat automated) methods of splitting DB. The first had no HSQL update (used v1.8 I believe) and the latter uses HSQL v2.x and also provides some portability if the macros aren't touched.

I can easily reproduce your problem (except for the inserted class paths - baffling) by moving an older type split DB to a new location. Only have to change two things to fix this. Using a BACKUP COPY (always protect yourself), open the .odb with an archive manager. Right click content.xml file and open with a text editor. Look for:

data-source-setting-value>file:THE DIRECTORY CURRENTLY POINTED TO/hsqldb.jar


and change it to the correct location of the driver directory of the .jar file. Save the change and update the file in the archive. Second, run the .odb and from the menu select Edit->Database->Properties... and make sure the directories in the Datasource URL are correct. Those two steps should fix the problem.

With a newer split DB there should not be a problem moving the DB around (I have not experienced any). However if things were somehow changed, look at the same items previously mentioned.

Edit 12/12/2016: At this point it may be best just to move this all over to another (probably newer) split DB. Follow these instructions:

• Create new directory.
• Place copy of database sub-folder from existing split DB into this new directory
• Create sub-folder named driver in this new directory
• From this post get hsqldb.jar v2.3.2 and sqltool.jar (both about halfway down article in the text) and place in the new driver subfolder
• Also place a copy of that hsqldb.jar v2.3.2 file in the main part of the folder for initial start-up (don't need afterwards)
• From same post, get split wizard .odb and place in main folder
• Run wizard and table(s) should be available
• Finally, with new DB open, run old split .odb - forms, queries, reports and macros can be copied and pasted into new DB.

This should alleviate headaches of moving the folder around. It automatically resets location when moved. However, if you're still looking at using Dropbox, make a copy of the entire folder first for safety.