database perfomance accde mde

Question

if I let access analyse the performance of my accdb database I get the tip "save it as an MDE database"

shouldn't it be accde ?

saving it this way , do I gain performance or is it only useful to protect the code

Answer 1

>>>if I let access analyse the performance of my accdb database I get the tip "save it as an MDE database"

shouldn't it be accde ?<<<

According to your description, an MDE file cannot become decompiled, so your Visual Basic code always runs at top speed. Additionally, since no source code is stored in the MDE file, the database loads faster and uses less memory.

The ".accde" extension for Access 2007 and later files that are compiled into an "execute only" file. It takes the place of the .mde file name extension that is used in earlier versions of Access.
An .accde file is a "locked-down" version of the original .accdb file. If the .accdb file contains any Microsoft Visual Basic for Applications (VBA) code, only the compiled code is included in the .accde file. As a result, the user cannot view or modify the VBA code. Also, users who are working with .accde files cannot make design changes to forms or reports.

Do you convert an Access 2003 database to the .accdb format? which version is Access?

For more information, click here to refer about Developer Considerations for Choosing File Formats in Access 2007

Answer 2

my database is converted to access 2010 ,accdb . but it is in the database analysis that access tells me to save it as an mde...... although saving it to accde is no problem

Answer 3

If you have an accdb then you create an accde. (if it is mentioning mde, then it is a mistake or you have an mdb)

It may have a slight performance benefit, but in my experience it is minor.  I don't use compiled version (mde/accde) for any performance benefits, but more for the added security that it provides.  It doesn't allow users to mess around with forms, code ... minimizing the trouble they can make for themselves.

The best performance tip possible is proper database structure, queries that don't pull more fields or rows then you actually use, good clean code, and creating a persistent connection at the startup of your database.  Also, ensure each user has their own local copy of the Front-End.

If you truly want to take things to the next level, then you could take a serious look at: Performance Tips To Speed Up Your Access 2007 Database which applies to any version of Access, not just 2007!  There is a lot to absorb.

---

Daniel Pineault, 2010-2012 Microsoft MVP
http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 4

it is an error , I created a brand new little database in access 2010 and the analyzer gave me the same tip to save the database in a mde. database ...   so nothing to worry about , many thanks