Attempt to make MDE locks up Access 2003

[RonT]

I have been attempting to take an Access MDF and turn it into an MDE. I've
read the Access notes on the procedure and scanned pertinent KB articles and
several of the message boards for accumulated experience, to no avail.

Here are the particulars:
* I am using Access 2003.
* The application consists of a primary (code) database, and a referenced
(data) database. They are both in Access 2002/3 format.
* As per the Access notes, I created a MDE file out of the referenced
database (no problem) and changed the table references in the primary
database to now refer to the MDE file.
* I have compacted the primary database.
* I have COMPILEd the primary database modules with no errors.
* There is no special access control in effect on the databases, they reside
in directories to which I have full access, and there is plenty of free space
in the volume.

When I attempt to create a MDE out of the primary database, I am prompted
for a new file name, to which I give a new unique name (extension defaults to
MDE). Once the filename prompt is confirmed, Access 2003 goes into a tight
loop, apparently infinite (I've let it go as long as 15 minutes before
killing it). It creates a file called db1.mdb of approximately 950KB. Once
it settles into the tight loop, Access 2003 consumes effectively 100% of the
CPU, yet does no further I/O. Access 2003 is otherwise non-responsive, and I
have no alternative but to force-kill it. After Access 2003 is killed,
attempts to open the db1.mdf file are met with hundreds of run-time errors,
indicating that the file is not usable.

This sequence is completely repeatable.

The consistent error, the lockup and the absence of any diagnostic
information make this very hard to troubleshoot. Any assistance would be
greatly appreciated.

Thanks,
Ron

 

[Ofer]

Hi Ron
Just recently something very similar happen to me, I tried to create an mde
file, and I had the same problem as you did.
Took me a while to figure out what is going wrong, when I compiled the code,
I got no compile errors, but one of the forms got open, when I closed that
form, I was asked if I want to save the form, I kept saying no.
When avantualy I said yes for saving that form, every thing got back to
normal.

I dont know if you have the same problem, but it worth trying.

 

[RonT]

That appears to be the problem and solution. I had tried compiling, but not
re-saving each of the (silently) affected forms. After re-saving each form
that was opened as a result of the compile, I was able to successfully create
the MDE.

Thanks a bunch for the tip.

Ron

 

[Tony Toews]

I have been attempting to take an Access MDF and turn it into an MDE.

Glad to see you've got an answer however...

* The application consists of a primary (code) database, and a referenced
(data) database. They are both in Access 2002/3 format.
* As per the Access notes, I created a MDE file out of the referenced
database (no problem) and changed the table references in the primary
database to now refer to the MDE file.

You don't need to make the data.mdb an MDE. It shouldn't have any
objects other than tables and relationships in it. And maybe one
startup form that warns the curious to not touch anything.

When you state table reference do you mean the linked tables? Or
otherwise?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[RonT]

Yes, the data.mdb is referenced only via linked tables. From your answer it
sounds like I can skip converting it to MDE, which would be lovely. I shall
try that. Thanks.

Ron