Secondary menu

Corrupted Database File?

I accidentally double-clicked my ESPlanner database file. Microsoft Access started running and gave me a "file corrupt" warning. I exited MS Access right away.

What should I do next? Is Access reliable in evaluating the ESPlanner database? I see that Access has a file repair utility--should I try to repair the database?

If I recreate my whole profile, I'd just be changing a tiny fraction of the 35 MB file and it seems that I might still have a problem.

Thanks for any suggestions.

Richard G

1

The database is compatible with MS Access. You can try the repair utility in Access. If you also use the Exit and Save Copy program from ESPlanner, which runs much the same code as is used in Access repair/compress. This is a good idea to do from time to time, if not after every use, to save a backup.

2

Thanks for your response, Lowell.
I used Exit and Save to make a backup. Tried to run Access repair/compress, but it won't run. Access continues to report original and backup database files are corrupted.
Next?

3

I can't say why the Access utility won't run or why it would report the file as corrupted. If it continues to work, then it works, and I wouldn't question it. I would make a backup every time I run.

Otherwise, it's time to start over. Open a support ticket and I'll post an empty database for you. I would have ESPlanner make its own backups but anti-virus software doesn't usually like that kind of business.

4

I'd better start over with an empty database. Maybe database file corruption is to blame for the 7 percent change in consumption recommendation I experienced a few weeks ago after downloading new update.

Will open a support ticket.

5

Changes in consumption people discover from the last time they ran is a very common thing. The rules for social security, taxes, etc are changing every day and this can account for it. Also, check those inputs carefully between different years. Sometimes, something you forgot about changing is responsible.

Dan is working on a FAQ page for this topic.