1
Support / Re: database file appears corrupt
« on: October 06, 2010, 07:14:30 am »QuoteShould i be getting a notification or anything if it was successful or not?
I don't know. I've never had a corrupt database to try it on. But according to this source...
-v[alidate] – Check database for validity. At the same time, errors are reported and repaired.
-f[ull] – Use with the -v option. Checks all records and pages and releases unassigned record fragments.
...so you should see something reported—if it finds anything.Quoteit doesn't seem to do anything other then briefly open a command prompt.
If, when running gfix -v -f movies.pvd, all you get is a flash of a command window, something is wrong. When I try it on my database, it takes 2 - 3 seconds. This would be easier for you to judge if you run it from a command window (run cmd.exe).QuoteAs for the backup I create a new copy of my database every time I add more titles (labeled as current # of movies).
As you now know, that's not an effective form of backup. It's fine for providing a means of recovery from an inherently risky operation or anything you might want to change your mind about. But the chance of a database error happening and you realizing it has occurred (before discarding good backup) are pretty slim. Effective backup should be automatic, regular and retain as many versions as possible. That can be done with a system wide backup routine, or a simple utility that can be scheduled to make regular copies of critical data.
I got it working from file directory using cmd and this is what I get when running both commands
I'm not sure what to do now tho. It doesn't seem to have fixed anything, even though I ran the fix command
Thanks for taking the time to help. If I ever get this fixed I'll have to come up with a better backup system.