By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,677 Members | 1,272 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,677 IT Pros & Developers. It's quick & easy.

Code compiles, mde creation fails

P: n/a
DFS
The .mde creation just sits there, until I click on the blank screen and I
get a (Not Responding) message in the title bar.

The code compiles fine. Other systems of a similar large size compile and
..mde create fine, so I think it's not Access but something in this .mdb.

Any ideas?

Thanks

Dec 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

DFS wrote:
The .mde creation just sits there, until I click on the blank screen and I
get a (Not Responding) message in the title bar.

The code compiles fine. Other systems of a similar large size compile and
.mde create fine, so I think it's not Access but something in this .mdb.

Any ideas?

Thanks


Yes. This happened to me also. The reason it happens is when you code
in VBA in access and have Events assigned to controls that don't exist,
or forms that you renamed. Cleaning up your vba code will allow you to
compile into an mde.

For example, In my case, I started out with a button named "button_34"
Which I added an Event "On Click". I then renamed button_34 to
something more meaningful, and added the new "On Click" method. Yet
the old button_34 code was left in the vba source, and hence I could
not create an mde. When I removed the unsused button_34 code, mde
creation worked.

Dec 13 '05 #2

P: n/a
DFS
Karen Hill wrote:
DFS wrote:
The .mde creation just sits there, until I click on the blank screen
and I get a (Not Responding) message in the title bar.

The code compiles fine. Other systems of a similar large size
compile and .mde create fine, so I think it's not Access but
something in this .mdb.

Any ideas?

Thanks


Yes. This happened to me also. The reason it happens is when you
code in VBA in access and have Events assigned to controls that don't
exist, or forms that you renamed. Cleaning up your vba code will
allow you to compile into an mde.

For example, In my case, I started out with a button named
"button_34" Which I added an Event "On Click". I then renamed
button_34 to something more meaningful, and added the new "On Click"
method. Yet the old button_34 code was left in the vba source, and
hence I could not create an mde. When I removed the unsused
button_34 code, mde creation worked.

That did it. I found 4 one-line "orphaned" routines in my main interface.
Deleting them let me create the .mde.

Thanks


Dec 14 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.