Ask Your Question
0

can't open .odb file [closed]

asked 2012-07-30 20:14:09 +0200

jdk10s gravatar image

updated 2015-10-22 23:16:43 +0200

Alex Kemp gravatar image

I have a .odb file that I created using Libre Office Database. I opened the file yesterday. Today, when I try to open the file, I get a request for a filter selection. Please advise

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by Alex Kemp
close date 2015-10-22 23:16:50.883510

Comments

1

Where did you save the file? In a pen?. Also remember that Base it's a embedded database, only when you do the save, the data is written to disk.

m.a.riosv gravatar imagem.a.riosv ( 2012-08-11 00:07:41 +0200 )edit

2 Answers

Sort by » oldest newest most voted
0

answered 2013-02-22 06:03:09 +0200

qubit gravatar image

Hi @jdk10s, @JohnD,

The LibreOffice devs take data loss seriously. If you guys are experiencing problems with our own native file formats, that will probably motivate them even more to tackle this problem.

If you do find a set of reproducible steps for this bug -- or even if you have a good inkling of what's causing it (e.g. @JohnD's notes), please file a bug about this problem, and the QA team will try to help you track down this issue. There are a number of things we could do to isolate what's going wrong, including taking a look at a version of a file that's working, and a version of a file that's corrupt.

edit flag offensive delete link more
0

answered 2012-08-10 22:56:27 +0200

JohnD gravatar image

There seem to be some bugs that still cause this to happen. I just had the same thing happen with a database I have been using for quite some time. I thought it might have been related to a fragmented file after a number of adds/deletes, etc. so after a significant amount of use I would execute the sql command -shutdown compact-. That seemed to make things a little more stable and reliable until I encountered the same problem after just one simple record deletion. There just doesn't seem to be a way to ensure data safety. This is a very bad problem when you expect to have a reliable way to store information.

I am using version 3.5.5.3 and am reluctant to try 3.6 since there have been some Base stability reports for that version as well.

Sorry, but I cannot offer any solutions. I would like to file a bug report but cannot get any kind of a handle of how or when this problem pops up. I have resorted to making frequent file backups and hoping for the best.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2012-07-30 20:14:09 +0200

Seen: 1,842 times

Last updated: Feb 22 '13