You open Profiler and the wrong covers are showing for each DVD or some other issue; the first action taken is usually a database repair. But how often do errors appear in your local database?


Every few weeks we get another member who learns their problem is easily fixed by this somewhat undocumented/not-so-obvious feature. I'm just curious how often those of us who have known about the feature for a long time must use it to fix a problem.


I can only recall one time that a database repair was required to fix an issue, but that's all -- even though I may open or change things in Profiler once a week. Perhaps I rarely end up with errors because I do run a dbr just before creating a backup every few months (to remove orphaned cast, crew, and studios.)

I get them on a fairly regular basis - this despite the fact that I routinely run a DB Repair every Sunday.

One that crops up the most is a prompt alerting me to the fact that the program did not shut done properly along with a notice asking me if I want to run a DB Repair.

I'm sure there are even some errors that get fixed before I become aware of them.

I get them often now. But it may be from adding 50-100 profiles and then removing them after original titles and produced years are corrected and contributed.

Small price to pay to clean up CLT.

I generally get errors after I "reassign collection numbers" (so that the most recent acquisitions have the highest numbers).  The first time it's generally okay, but after a couple of reassignments, things get f'd up and the repair needs to be run.

I get the "program did not shut down properly" when I lose power, but I generally don't run the repair and usually things are fine in these cases.

"When in despair, do a repair!" 

I had to fix my main-db maybe 3 or 4 times in 12 years.

Quoting Wigram:

Quote:
The message asking to run a DB repair have all but disappeared since I give time to the program to shut down properly. I used to close the program and shut down down the computer immediately after at the end of the day. Then, I would often get an error the next day...

Hm, you might be on to something here. Sure this shouldn't happen, the programs should all shut down properly before the system-shutdown, but if you worked long enough with computers you know better than to rely on "shouldn't happen" 

Quoting ateo357:

Quote:
I get them often now. But it may be from adding 50-100 profiles and then removing them after original titles and produced years are corrected and contributed.

Why not use a second db? I have recently retouched all covers that have rating logos (Hate those with a vengeance!), and to replace the missing parts of the covers I downloaded all similar ones to look for candidates. But I did that on a secondary db to prevent that I accidentally screw up my main-db.

cya, Mithi

Quoting scotthm:

Quote:
and when Profiler opens back up all the cast (and possibly crew) are gone from the profiles.

Never heard of a behaviour like this and am quite sure that this isn't supposed to happen.
Since this seems to happen quite frequently on your machine(s), I'd suggest to open a support-ticket.

Every once in a while when opening profiler I get an error stating that certain profiles in my database could not be loaded. I run Db repair and it corrects the problem. I have this happen at least 3 times this year and it is never the same profiles.

I've been using the program well over 10 years now and I don't recall even needing to run it.  I have from time to time just to make sure.  But I've never needed to do so.