Possible Fix for "Unable to create MDE" Error and "Unexpected Error 40230" in Access 2002

Hi

I thought I'd post this in the hope my experience may help others avoid the
problems (and significant amount of time) trying to recover from the above
errors when trying to create an MDE in Access 2002. As I haven't seen this
solution posted anywhere before I hope Microsoft might also take a look to
see if it might be a common cause.

I'll give you the answer first... move the mdb to a local disk on your PC,
C&R it, compile it and create an MDE on the local disk. That's it.

*************

Now I guess many developers will already be working locally in which case
this may be of no help but for me this was the solution after *everything
else* failed.

Faced with having to reconstruct a huge and complex database I spent many
hours trying to compare the failing db with earlier "good" builds to
determine which objects were causing the problems.

With each one I progressively deleted more and more objects in the mdb until
it would create an mde. Knowing the last group of deleted objects then
allowed the creation of an mde suggested the problem object was in that
group just deleted. But starting over with an original mdb and just deleting
that group of objects again DID NOT then fix the problem.

Stepping back through recent similar builds showed each build behaving
differently when I tried to repair them. One would not create an MDE with
virtually every object deleted. I came to the conclusion the problem (on
this occasion at least) was not necessarily in my objects at all but with
Access's systyem objects.

I moved the mdb from the network drive to a local drive to speed up testing
only to find the problems went away!!! Very pleased, obviously!, but
confused too. So then I did a C&R on the mdb and moved it back to the
network... guess what?... now it works fine on the network drive also.

So... although I have a very large db (30 linked tables, 700+ queries, 80
forms, 400 reports and LOTS of code) it doesn't appear this overall number
of objects is the direct cause.

HTH
Mark Potter

My network is peer to peer 100mbit. Dev PC is WinXP SP1. Network drive is on
my WinXP SP2 "server".







.

Relevant Pages

  • Re: Lock / Unlock VBA project
    ... "Alex Dybenko" wrote: ... make MDE? ... library MDB - create ne mdb, import forms/modules from your app, which ... have to make MDE of it and add reference to library MDE in order to make MDE ...
    (microsoft.public.access.modulesdaovba)
  • Re: Converting Access 97 MDE to Access 2003
    ... what is the MDB front-end you are ... The mdb front end is of course the original mdb you had to make the mde. ... ms-access is the in the SAME VERSION as what you are developing under. ... a mde file is created by going tools->database utile. ...
    (microsoft.public.access.conversion)
  • Re: 5 access 2000 users and 1 AccessXP user
    ... > Making the user an administrator on the local machine worked for the case ... > it to th PC (it is an mde file). ... The back end is on a server running win2K ... locate the front end mdb file on the ...
    (microsoft.public.access.conversion)
  • RE: Function name not found
    ... but shouldn't the MDB use the same references? ... something happen in the MDE compilation process that disallows the XP machine ... I have this startup methodology that provides a little more flexibility than ...
    (microsoft.public.access.modulesdaovba)