Scanning for unused blocks

[weseverett]

Ok, for better or worse I moved my 4000 field DB over to 7.0 v3. I have a few relational DBs connected primarily to moved scanned PDFs out of the main DB (storage purposes). After having crashed a couple of times, now, upon reestablishing the relationships "scans" for unused blocks EVERY TIME.

Wasn't doing this trick the first month after I converted, but it is now the normal course of action.

This totally sucks as it takes like 30 minutes to cycle through it. Considering moving the scans to a new DB and renaming over top of it.

Any thoughts would be appreciated.

Wes

[FMDuck]

FM7 handles corruption much better than previous versions but if you migrate a pre-7 database to FM7, any corruption that already existed can become persistent.

I would first check your File References to assure that they are clean. Trace and remove duplicates.

Then try being on different layouts when touching the relationship. Most corruption in FM is in layout objects. You can sometimes delete the layout (COMPLETELY) close then reopen FM then recreate the layout from scratch.

It sounds like you may have corruption in a field definition though. If you think so, consider adding new fields for your key fields that are used in the relationships (DO NOT DELETE THE OLD ONES). Export your key field data to a flat file then reimport to the new fields. Leave the old fields and rename them to 'NeverDelete' or something similar but don't delete them. UNLESS the problems persist. If so, THEN delete the old key fields.

I don't have any technical info to back this up but have worked with some pretty large and screwed up databases. These approaches worked best for me.