I have created a database using LibreOffice. When I access the database, it crashes when I close it. I have read that I can split the database but have not been able to find instructions on splitting an existing one. Will this solve my problem with the database crashing? I also access it from a WiFi connection.
More info. What OS? What ver LO & is it a distro version? This shared folder is local (your machine)? Are you using any macros? Does it crash every time (ie: simple open & close immediately)? Splitting won’t necessarily cure the problem.
You can create a new split DB, open both old & new then simply do a copy/paste for each item (tables, forms, etc.). A tad bit slower but simpler.
It is on a shared folder on our server. Laptop is running Windows 7. Latest LO. Not sure what distro version means. no macros. yes, every time no matter what we do.
Have not seen but one other question like yours which involved the cloud and nothing but problems there also. Don’t have the setup currently to test your situation but believe it concerns HSQL which actually resides in LO. However, splitting the DB would place HSQL in the folder with the rest of the files involved. Still questionable in my mind. Most setups utilize an external DB such as PostgreSQL or MySQL or even HSQL running in server mode.
Regardless of why this is your mode of operation (there is always some reason/policy for the situation) it is never good to have valued information in an embedded DB. At the very least go with split or better yet, an external DB.
BTW - distro refers to a Linux distribution.
Thank you for your reply…
[Tutorial] Splitting an "embedded HSQL database"
https://forum.openoffice.org/en/forum/viewtopic.php?f=83&t=65980
I prefer this one as it includes the new DB and eliminated the extra hassle of dealing with the auto-increment problem.
I just found and ran that. It worked except for running it in server mode. That I still cant get to work.
This is a “black box” problem. You have a few options:
-
Sometimes you can copy your LO file, and delete objects in it find if there is a thing that you can delete to make it not crash. For example, start by deleting all your reports, forms, and queries, and testing to see if it still crashes. Then if it does not, go back and delete half of them and slowly with a binary search you can find what it making it crash. This has worked for me at times. Although I haven’t fully tested this, it appears you can drag and drop forms from one open database window into another, as a quick way to copy them.
-
If you can, restore from a recent backup that does not do this, then roll in your more recent changes. Yes, I know, this can be painful. It really pays at this moment to have recent backups, and I’m not talking about one file that you overwrite again and again, to backup but rather 100 different backups forming a date/time trail into your past, so you can test them backwards in time to find where it first broke, and begin to recover from there.
-
You might copy your tables and design into a new fresh data base, making sure to test it as you proceed to make sure you’re not re-introducing the same crashing problem.
I worked with MS Access for many years, and it has had many similar problems that I’ve had to fight sometimes on a regular basis. Even the version I use today has one nasty bug and if I do that one thing, even accidentally, then I’ll have to restore from a backup, or at a minimum wipe out the current form, and restore that form, loosing my recent edits in the process.