Disabling Access Menu Items

[MikeAngelastro]

Hi,

A client of mine has an Access application that is an MDB. I tried to convert it to an MDE to improve performance but found that the "Make MDE" menu selection was disabled.

How is that done and how can I reverse it so that I am able to make an MDE with that application?

Any Ideas?

Thanks,

Mike

 

[Rich]

What reason do you have for making an MDE? There is no improvement in performance by doing so

 

[MikeAngelastro]

Hi Rich,

I don't understand. I'm a little surprised by your question. When an Access application is run as an MDB, it has to compile the code as it goes along. Because the MDE is the compiled version of the MDB, this is not necessary and therefore the application runs faster. This is true, however, only if you are using VBA code. With tables, queries, and macros there is nothing to compile. So if your application only had these, then the MDE would not be any faster. In fact, the more VBA code your application has, the greater is the improvement in performance when you complie it to an MDE.

The other advantage is that the user can not look at the code and change it. This is also to be avoided.

What am I missing?

Mike

 

[ghudson]

I have seen your question before. If you have Access XP then your db is not really an Access XP (2002) db. The MDE option is disabled in Access XP if the db is not really an Access XP db. If you search this forum for the keywords "MDE" and "XP" I am sure that you will see more user info. I do not have Access XP but I have seen quite a few user posts just like yours.

Good Luck!

 

[MikeAngelastro]

Thanks ghudson!

It turns out that Access 2002 will load an Access 2000 app in 2000 format. Because Access 2002 adds info to the file when it is converted to an MDE and because this would confuse Access 2000, MS disables the ability to convert to an MDE whenever an Access 2000 file format is loaded. The solution is to convert the app to the 2002 format and then the ability to make MDEs returns. Another option is to load it into Access 2000 and convert it there.

I will have to varify this, but I think my client is using Access 2002 to run an Access 2000 app. It is a new client and I had not yet had a chance to get very familiar with what they have.

Thanks again for your help.

Mike