How do I recover a front-back DB
Posted: Fri Feb 22, 2013 7:16 pm
In an embedded odb....... 3> user> backup> My_emb_db.odb is a zip file renamed .odb containing 2 hefty files each about 4 meg +config stuff . and should just be a useable copy your odb complete with yesterdays closing data. currently about 8 meg.
In a filemode odb ........mydb.backup is just a Windows unrecognised filetype (a single file) in my case presently about 24meg (with different, not very similar data, but still 3 times as big as embedded) and mydb.data is about 24.5meg wheras mydb.file.odb (the executable) is a mere 0.05meg or 50k. 450k gone astray in housekeeping duties)
as would be mydb.server.odb (50k) if I kept its form.definitions etc synced up to the file version.
Now the nitty gritty:
I have no clue as how to use mydb.backup in the emergencies which it is presumably for, just now I changed its name to mydb.backup1 and reopened mydb.file.odb edited a couple of records to make sure and closed it again, and Yee-haa there's a new mydb.backup next to the old one but a tiny bit bigger, after the edits.
But what if someone mistakenly or maliciously trashed 75% of my datafile. How do I revert to last-days data because todays mydb.data now contains junk. at least I only lose 1 days stuff.
I note that even if my data shrinks that mydb.backup_newest still bloats, as does .data.
Also, please Where is 'ShutdownCompact' command? I've never found it. I thought it was supposed to be in tools
oh yes? oh no!
Perhaps if I try it in tools> sql.
Oh yes! sorry DACM, but wouldn't it just be a couple of loc's for 'em to stick it straight on the tools menu.
Thanx to all
We'll leave the autosave every few minutes versioning stuff 'til later
In a filemode odb ........mydb.backup is just a Windows unrecognised filetype (a single file) in my case presently about 24meg (with different, not very similar data, but still 3 times as big as embedded) and mydb.data is about 24.5meg wheras mydb.file.odb (the executable) is a mere 0.05meg or 50k. 450k gone astray in housekeeping duties)
as would be mydb.server.odb (50k) if I kept its form.definitions etc synced up to the file version.
Now the nitty gritty:
I have no clue as how to use mydb.backup in the emergencies which it is presumably for, just now I changed its name to mydb.backup1 and reopened mydb.file.odb edited a couple of records to make sure and closed it again, and Yee-haa there's a new mydb.backup next to the old one but a tiny bit bigger, after the edits.
But what if someone mistakenly or maliciously trashed 75% of my datafile. How do I revert to last-days data because todays mydb.data now contains junk. at least I only lose 1 days stuff.
I note that even if my data shrinks that mydb.backup_newest still bloats, as does .data.
Also, please Where is 'ShutdownCompact' command? I've never found it. I thought it was supposed to be in tools
oh yes? oh no!
Perhaps if I try it in tools> sql.
Oh yes! sorry DACM, but wouldn't it just be a couple of loc's for 'em to stick it straight on the tools menu.
Thanx to all
We'll leave the autosave every few minutes versioning stuff 'til later