Frank Schönheit - Sun Microsystems Germany wrote:
<snip>
Well, 2.0.4 was somewhat prone to data loss (for embedded .odb files) in
that when OOo crashed after you entered data without closing the .odb,
then you had good chances the data was lost upon the next OOo start.
This has been fixed (well, relaxed, there still are some more seldom
situations, unfortunately) somewhere on the way, I don't remember the
concrete version.
Without knowing the reasons for your anomalie - the recovery though
there wasn't a crash - it's hard to guess the consequences. If at all, I
think they would be for the embedded HSQLDB only, not for linked .dbf files.
Ciao
Frank
When I was using the linked .dbf and this happened, I think it may be
why my data got so royally messed up. I suspect it was "recovering" by
using some data buffer it had hanging around, and with no primary key, I
believe it was pretty much random where the changes went (sometimes in a
different record but not even into the same field). Now, with the
properly defined embedded database, I haven't noticed any contamination
of existing data -- although I have had to (re)enter data I'd have sworn
was already there. But then, my memory needs external assists, too!
I REALLY want 2.3. I'll follow up on this then, if it happens again. In
the meantime, I'll cancel the recovery if there was no crash.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
