[libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-17 Thread ptoye
Robert Großkopf wrote > here the macro for saving data while opening or running Base: Thanks Robert, that's fantastic. I'll try it out later this week. - Peter -- Sent from: http://nabble.documentfoundation.org/Users-f1639498.html -- To unsubscribe e-mail to: users+unsubscr...@global.libr

[libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-17 Thread ptoye
Thanks Robert, that's fantastic. I'll try it out later this week. - Peter -- Sent from: http://nabble.documentfoundation.org/Users-f1639498.html -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubsc

Re: [libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-15 Thread Robert Großkopf
Hi Peter, here the macro for saving data while opening or running Base: SUB DatabaseBackup(inMax AS INTEGER) REM A copy of the databasefile *.odb would be created in the Backup-folder. REM The amount is limited to 5 copies. After it has reached 5 copies, the oldes

[libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-15 Thread ptoye
Robert Großkopf wrote > You could use the macro for copying the file to the backup-folder of LO > when opening the file. It's published in the Base-Handbook. I could post > it here also. That would be very useful Robert. I've found that the corruption is happening when I close LO. So saving when I

[libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-13 Thread ptoye
Thanks, but at the moment I'm making manual backups. Unfortunately (?) it hasn't happened again. Very frustrating. - Peter -- Sent from: http://nabble.documentfoundation.org/Users-f1639498.html -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libr

Re: [libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-13 Thread zahra a
hi peter. if you are sure that your file is corrupted, just right click on it and find properties. in the security tab, find and select previous versions. then press okay button. it restores previous version (that worked properly for you). God bless you all. On 1/8/18, ptoye wrote: > I think that

[libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-08 Thread ptoye
I think that the first thing to do is to work out if the corruption's happening on loading or saving. It's easy to see what's happening as the corrupted file is of a very different size, so I can see it in Explorer. That at least will give me a handle on the problem. Then I can work out whether to

Re: [libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-07 Thread Robert Großkopf
Hi Remy, seems you haven't read the first mail of this thread: "If I try opening it in a Zip file reader I'm told it's not a valid Zip file." The way to repair a *.odb-file is described in the Base-Handbook in detail. But if you can't extract anything there you couldn't get data out of a corrupte

Re: [libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-07 Thread Remy Gauthier
Hi, This problem seems to have been observed not so long ago: https://ask.libreoffice.org/en/question/63369/repair-corrupt-odb-file/ The fix that is mentioned in that post is there: https://forum.openoffice.org/en/forum/viewtopic.php?f=83&t=17567 Not sure if the proposed solution will help, but it

Re: [libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-07 Thread Robert Großkopf
Hi Peter, > > Both LO and Java are 64-bit versions. Is it a good idea to revert to 32-bit > versions? I'm not sure how LO decides which Java to use if given the choice; > I assume it picks up the same bit-version. Bugzilla doesn't show any obvious > connection between 64-bit and database corrupti

[libreoffice-users] Re: Database corruption since LO 5.7.3 installed

2018-01-07 Thread ptoye
Thanks Robert. Restoring from a backup is exactly what I've been doing. But it's odd. It's a database I use about once or twice a week (depending on how much wine I've been drinking), and it's failed to open 4 times since then: the saved dates were 26 November, 24 December, 27 December and 5 Jan. I