I'm sure this sort of problem has happened to someone else before but if there's a fix given here in the forums, I couldn't find it so I'll ask here.

I've DVDP installed on the office PC and at home.  I've had this double-configuration for a few years and never had troubles until recently.  To keep both copies up to date, I'd create a full backup on whichever PC was most up-to-date and then do a full restore on the other PC.

Then one day I ran into problems. Despite running db repairs, it seems I can create a backup file yet that backup will not work to restore.  Attempts to do so will either hang at some early point in the 'Restoring Cast" operation or will report a "Jpeg Error #52" at approximatly the same point in the restore operation.

From what I've heard about this error type, it most likely means I've got a cast photo that may look, smell and feel like a good jpg file, but is either corrupt of is a different file type that was renamed with a jpg extension.

Is there any way I can determine which cast entry has this problem photo attached? It certainly isn't found by the repair utility, and if I'd never tried to restore from backup, I would have no clue that I was creating unusuable backup files.

I have had to basically abandon the full database and create a new one that seems to be error-free right now.  To do that, I created a new additional db location. I populated this new db by creating a 'Flagged Profiles' only type backup from my 'crap' db and then restored that to the new db.  The new db wound up with no more cast photo's (the original db still shows them though), but at least this new db appears to be stable now.

Assuming I'm correct - that I managed to have a corrupted cast photo get it - how can I prevent this from happening again and/or will it be possible for the db repair utility to 'discover and correct' such errors in the future?

Thanks for that other thread link - sure does sound like the same problem.

Well, now that I've got my rebuilt db, I'll start the process of populating cast/crew photos again.  But I'll certaily only do so in managable batches - noting which names I've updated and follow it up with a full back, then test that backup immediatly on a secondary db. Only if that backup is confirmed valid will I then go on to further modify my data.

Ken, if you're listening, perhaps this sort of problem can be either detected by the repair facility or an option can be provided to the user to bypass the offending jpg(s) during a restore so the user can at least salvage most of thier data in the future?

Quoting widescreenforever:

Quote:
can you do a restore by 'filtering'  ?  try not including cast photos upon restore and see what happens.. 

Actually, that was how I started the process of rebuilding a complete db w/ cast/crew photos again.  Took me a few days, but it's pretty much all back. It required me sifting through the entire cast list via pretending to be updateing cast on any profile.  I looked for multiple name entries (variations) where each entry had a photo - usually was the same photo - and cleared those out. Also found some entries where the name indicated it had a photo attached, yet no photo would actually display. Those I yanked completely out.