[Closed] General Error. // Input/output error.

[Kirjava]

I was checking entries on a table.
I saved and closed the table.
The whole thing closed.
Now it says input/output error (if it opens at all).

Unpinned the database.
Re-pinned the database.
Restarted laptop.
Now Base wont open at all.

It's 840kb and I really don't want to lose it.

Tried to open some other stuff in OpenOffice Writer, that wont open either.
NOTHING saved in any ODwhatever will open.
My diary since 2007.
My list of all DVDs/Books/Games.
Everything I've ever written in the last decade.
Locked.

[UnklDonald418]

If nothing in OO works, try resetting your user profile.
Open Windows Explorer and in the address bar type
%AppData%
Navigate from there to OpenOffice>4
Rename the folder named user to userOld
Now attempt to open one of your OpenOffice documents.
You should get an OpenOffice registration dialog
Once completed the document should open.

Your signature indicates you are using version 3.1 which is 10 years old. You should consider updating to a more recent version.

[RoryOF]

If that doesn't work, start TaskManager (Ctrl Shift Esc) and kill any soffice processes shown on TM's tabs. Then see if OO will start.

[Kirjava]

Task Manager can't see it.
I tried LibreOffice but it was so flaky I gave up.
LibreOffice did at least tell me the database was corrupted.
Deleted the offending database, hard reset laptop,
uninstalled/reinstalled and started database from scratch.
218 items of who knows how many already restored.
This tine I'll keep a backup. Thought I had one but can't find it.
Automatic backup only produced a writer page with half a line of nonsense.

[UnklDonald418]

Regular backups are highly recommended when using Embedded Base databases because they are susceptible to corrupt ,odb files. Laptop users seem to have it happen more often, possibly when they fold the screen down before the .odb file is completely written to the hard drive.
An odb file is actually a zip archive so after Base is closed it can take several seconds to compress the data and write the file.
Because the table data is stored in a separate uncompressed file, a JDBC connection is safer.but there are trade offs.
[Wizard] Create a new 'split' HSQL 2.x database

[Kirjava]

That'll be what happened then. When I saved the table it crashed, so it didn't get a chance to save properly.