CRASHED BASE after several mods

[LSemmens]

I have a database for my stamp collection. It as been normalised with numerous related lookup tables. Given that there was an issue with default values I had to go back and convert many fields to all caps to permit SQL to update the default values. The SQL commands all completed normally and I went back and changed the relations to allow for cascading of updates and setting defaults on delete. Now I get the attached error on screen whenever I even attempt to open the database. I cannot open anything to let me either correct, or extract the data from the tables.

The question being is there an easy method to get to the data, or should I write it off (not a desirable thought, but I CAN live with it)

[EasyTrieve]

Food for thought: As I work with base, I regularly make rotated backups of both my front and back ends. Before I did things this way, from time to time, I lost considerable time and work. Databases like LibreOffice Base are very complex, and there are many and considerable bugs in it. BTW, MS Access when I last used it had similar unfixed issues. So far MariaDB as a back end has been more stable, but I still back it up. (I use LO as a front end to it.)

[Ratslinger]

Hello,

Typically when there are script errors, it is a serious problem. Without the actual Base file can only suggest looking at answer in this post → OpenOffice file: The database was created by a newer version of LibreOffice. Have had success with this in past.

Best to avoid HSQLDB embedded files. Have a history of this type of problem. This is one reason why it is being replaced with Firebird embedded - a better choice.

[LSemmens]

Thanks for the suggestion. Strangely enough, I have not had success opening any database files with an archive manager, not just this one. I’ve spent the evening re-creating the database anyway, which, in some ways is a good thing because I can tidy up some of the tables and forms that I use. It is a perfect example of why you should keep a current back up of everything you rely upon. (In this case, I thought I did have a backup, but it was several generations old, so was not as useful as I had hoped.) Fortunately, the data in the lookup tables was still current, so All was not lost.

Thanks for trying. MY BAD, I forgot some critical info
Libre Office
Version: 6.0.7.3
Build ID: 1:6.0.7-0ubuntu0.18.04.5
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: en-AU (en_AU.UTF-8); Calc: group