Decompile vs. Recreate?

[Rick Roberts]

Is there a school of thought regarding decompiling an MDB vs starting with a
new shell and importing everything including relationships and toolbars?

The reason I ask this is that I discovered early on that even decompiling
didn’t wipe away all my sins (or is that MS Sins). It was actually much
cleaner to start anew.


I know that when I use the import method the relationships are all there
but the layout when you view them has not been maintained. Also, I do seem to
notice some new indexes afterwards but I am going to clean those
programmatically before deployment Other than that is there a shortcoming?


Thoughts?

 

[Graham Mandeno]

Hi Rick

It all depends on the heinousness of the sin (and your degree of
desperation!)

I usually try a compact/repair as a first act of penance, followed by a
decompile, and finally a complete recreation as a last resort. (A
born-again database?) Actually, there is another, more drastic measure,
which is to save all the objects as text (using the SaveAsText method) and
then load them into the new, empty mdb with LoadFromText.

The most important thing to remember, though, is *ALWAYS* take a copy of the
mdb file before trying anything, because sometime a compact/repair or
decompile can actually worsen the sin to the extent that your beloved mdb is
forever consigned to purgatory!

(BTW, I love your metaphor ;-)

 

[Rick Roberts]

Thanks,

I Compact On Close as this is an in development process with heavy coding.
Lots of recompiles. I ran into problems early and found the decompile option
but as I said, that didnt take care of things bad. But a full recreate did.
It's amazing how much smaller the resulting file becomes.

I have to be honest in that I have never heard of your last option of
deseration. I'll have to remember that one.

Rick