Limits on Making an MDE

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Access 2003 ..Windows XP Pro

Is there a general set of guidelines on file size and conversion from an MDB
to an MDE? I have made an initial try, but did get an error message about
compiling large database into an MDE file.

I have seen a reference from Doug Steele MVP in using the Deubug tool from
VB Editor to correct all errors. Before I get too carried away with this, I
am wondering if some re-design or further splitting should be considered.

My database has been split into a front and back end. The front end has been
"Compacted and Repaired", and is now 18.8 MB (18,796 KB) which includes the
following objects:Should I be concerned that the size is getting unweildly, and I am headed to
the performance limits?

As always ..... Thanks in advance.

Keith
 
No issue with size there. 19MB is not too large, and even if every form and
report had a module, you have < 200 modules.

Suggested sequence:

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

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, and compact again.

5. 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

6. 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.

You are aware that you need to use the Access 2002/2003 file format (not
Access 2000) in order to create an MDE in A2003?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

message
 
Thanks very much Allen,

Your time spent adding such clarity is very helpful, and truly appreciated.
The information I was seeking just did not seem to be out there anywhere, but
obviously a part of your collected experience.

I followed your great guidance and have happily acheived success and a fully
functional MDE. Just like it is supposed to be.

Thanks ...Keith
 
Back
Top