| Registered: December 24, 2007 | | Posts: 42 |
| | Posted: | | | | Pulled up Profiler to add some DVDs and it just started to hang. I couldn't end it correctly and tried to end it through Task Manager. Still hung up, so I rebooted. Came up and asked for a DB repair and I ran it, but got this error.
DBISAM Engine Error #11013 Access denied to table .... DVD Profiler\Databases\Default\Collection.DAT
the DB repair is still running, but I fear I may have worse problems. Any suggestions. |
|
| Registered: December 24, 2007 | | Posts: 42 |
| | Posted: | | | | The DB repair finished (with the error) and looks OK when I randomly check it, but don't know if I can trust it to be good.
What should I do to ensure my collection is OK. | | | | Last edited: by ThatsAllFolks |
|
 | Blair | | Resistance is Futile! |
| Registered: October 30, 2008 |  Posts: 1,249 |
| | Posted: | | | | If everything looks ok, then likely DB Repair fixed everything and it is just fine again. What you should do right now is make a full backup of your database (File -> Backup Database... -> Full Backup") making note of the error, and set it aside. However, when you just said that Database Repair finished "with the error," are you saying that it finished running and everything looks fine, or are you saying the error was mentioned in the DB Repair as if it did not fix the problem? If you are saying the second choice, then, assuming a contact-report message did not appear asking if you would like to send a report to Invelos, go to the Contact Us page (there is one at the bottom of each page if you don't click this link) "Technical Support, Support Question -> Open a new technical support ticket" and send a message being very specific with the errors and what you have done already. Only do this, though, if it looks obvious that the error was not fixed. | | | If at first you don't succeed, skydiving isn't for you.
He who MUST get the last word in on a pointless, endless argument doesn't win. It makes him the bigger jerk. | | | | Last edited: by Blair |
|
| Registered: December 24, 2007 | | Posts: 42 |
| | Posted: | | | | Quoting Blair: Quote:
If everything looks ok, then likely DB Repair fixed everything and it is just fine again. What you should do right now is make a full backup of your database (File -> Backup Database... -> Full Backup") making note of the error, and set it aside.
However, when you just said that Database Repair finished "with the error," are you saying that it finished running and everything looks fine, or are you saying the error was mentioned in the DB Repair as if it did not fix the problem?
. I'm saying the first option. It finished and everything looks fine. On a safe note, i reran the DB repair and it finished without any errors. So I guess everything's OK. I'm doing a DB backup now. Thanks for the reply |
|