decompile questions

[Robin]

The previous post/answer by Allen Browne sounds like just what the doctor
ordered for my current situation. An intermitent "Access encountered a
problem ..." cropped up recently during multiple changes to my DB. But it
references access 2002, I am wondering if there are adjustments or anything
additional I should consider as I am using Access 2007, accde FE and accdb
BE, under the runtime environment.

Also, am I correct to assume that both the FE and BE should be subjected to
the same procedure listed below.

Thank you,
Robin

Copied from previous post:

Answer
Subject: Re: MDE problem 11/28/2006 7:49 AM PST

By: Allen Browne In: microsoft.public.access


A decompile will probably fix this but try this sequence as it deals with a
number of possible issues:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again. Close the database without running any code.

5. Create a new (blank) mdb in Access 2002 format. Before you do this, you
may need to set the Default File Format) under:
Tools | Options Advance.

6. Immediately turn off the Name AutoCorrect options.

7. Import everything from your old database:
File | Get External | Import

8. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

9. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
and the code syntax is compilable.

 

[Douglas J. Steele]

You can't decompile an accde, although I assume you could decompile the
accdb and recreate the accde from it.

As well, I don't believe you'll be able to decompile the application using
the runtime, as decompiling is a design change, and the runtime doesn't
support design changes.

There's no reason to decompile the back end, since decompiling works on
code, and there should be no code in the backend.

 

[Robin]

I see that I was a little misleading. I am using the .accdb now to develop
the project with the full version of Access 2007 and will be performing these
actions on the .accdb FE "prior" to the creation of the next and hopefully
final version of .accde FE which will be distributed using runtime.

I can remove the limited code that was in the .accdb BE that removed the
subdatasheets, as help from the newsgroup has shown me how to do this from
the FE

My current testing of the .accde at runtime is where I am experiencing the
intermittent glitches. So I'm trying to use better habits as a developer and
build stronger installs.


Thank you,
Robin