I put it down to entropy theory, others may see it differently.
When an ACT! database breaks you may be able to fix it, but perhaps not.
At this point, tech support will say, "the only way to recover your database is to create a brand new one and then import the data from the old one"
Fine with an unmodified database but if the original was heavily cusomised this can be a big chore.
Now the built in options that exist are Save Copy As... either a Copy or an empty copy.
To be honest, I'm not 100% sure what process is used to create these, but is suspect it's a case of simply duplicating the existing database and renaming it. Yes, the custom fields are preserved, but so are the original glitches.
So, more in hope than expectation, I would like to propose a third option.
A facility, that with a single click will create a brand new database, then import all the custom fields and layouts from the old one, and finally do a full data import from the old database to the new one. And then do a conversion check to determine the data was transferred successfully.