A funny thing happened while compiling my project. (Access 2002)

Topic

New Reply

All right. I’m new at this XP stuff, but it seems no better than 97. Actually, worse for me, because of the learning curve.

I’ve been working on a project for a few days, compiling my project (mde) and then changing it and recompiling. Everything was going okay. Yesterday, when I tried to compile, a few times it just sat there, but rebooting my pc and repairing the db would get it moving again.

Today, I can’t seem to compile my project at all. It sits there on the Make MDE/ADE screen and does nothing, until I click on the close button and I get a message that my project is not responding, and I have to End Now.

A few times, I got an error box saying that it was sending a message about the error and restarting. Of course the error meant nothing to me.

Is there some quirk that I’m missing? Like the IsNull(FieldName) error, where you had to specify True or False, or you’d have containers that wouldn’t close?

If anyone has any ideas, I’d be SO grateful. I’ve tried importing all of my objects into a new db, but that didn’t help one bit. I still can’t compile my db.

Frustratedly yours,

Cecilia

Reply | Quote

Replies

Cecilia,

I am slightly confused. You say you are compiling your MDE project. However, an MDE is a converted MDB that stores compiled code. Did you mean compiling your mdb??

Which operating system are you using, i.e., Windows XP or other. I would suggest checking your references in the new database to ensure all is properly set and then retry compiling. I have not encountered any problems using 2002 and compiling the databases except when the references weren’t set properly.

Reply | Quote

Sorry, I am compiling FROM an mdb TO an mde. My frustration got in front of my clarity *g*

OS is WinXP. I’m pretty sure the references are correct, otherwise this would have been happening all along.

Cecilia

Reply | Quote

Hmmm, maybe I fixed my own problem, or maybe it’s just another temporary fix….

I opened the module and compiled from the debug window. When I went to create the mde again, it worked fine.

I think there are ghosts in my machine, taunting me.

Reply | Quote

You have two different compiles going there. The compile you do from the VB editor will show up problems in your code and should theoretically compile all the parts of the project that have gotten decompiled or partially decompiled as you worked with them. The compile you do when you make an MDE does something else again. If you run into those problems with any version of Access, including XP, the customary fix is to first decompile the project, then close Access and restart it before doing a compile from the Debug menu in the VBE. That usually gets rid of the most persistent ghosts.

Reply | Quote

Thanks Charlotte! That’s pretty cool! I didn’t know you could do that stuff!

Can you recommend some reading material (website/book/other) where I can learn these more advanced things?

Cecilia

Reply | Quote

Do a Lounge Search in this forum on Access books and you’ll find numerous threads on that question.

Reply | Quote

Hi Cecilia:

Hope you

Reply | Quote

That’s a great link, John, and we prefer posting a link to the site rather than pasting someone else’s work here. I changed the subject line of your post so that there are some trigger words for those doing a search. That and the same words within the post should help a lot the next time someone goes looking for an answer to why their database has gotten corrupted. Thanks.

Reply | Quote

WOW! John, that is great!

LOL, yes, I’m sorry I asked *g* A lot of work for me!

Thank you so much for the link, it is one that I have never seen before.

Cecilia

Reply | Quote