Make MDE File Causes Access 2003 to Stop Responding

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

JamesJ - 12 Apr 2005 21:19 GMT

Has this happened to anyone else? I have a form which is
sort of like a switchboard form. The form contains 2 list boxes
which are populated with select statements. The form also has a
custom menu that contains the Make MDE File. Here's what happened.
When the select statements for the list box(s) are in the OnOpen of the
form and I select Make MDE File access closes and reopens the db
and everything runs fine and the MDE gets created. But, when the
select statements are in the row source properties of the list box(s)
access closes the db and then stops responding.
I looked in the knowledgebase briefly but didn't find anything that I
considered pertained to this.

Thanks,
James

Reply to this Message

Allen Browne - 13 Apr 2005 05:16 GMT

James, I'm not really clear on this. I think you are saying that if you save
the SQL statement in the RowSource property of the list boxes, then A2003
hangs when you attempt to create an MDE, but if you leave the RowSource
blank and assign it in the Open event of the form it does not hang?

If so, this is probabably a corruption caused by either Name AutoCorrect or
a compilation error. Try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

Signature

Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

> Has this happened to anyone else? I have a form which is
> sort of like a switchboard form. The form contains 2 list boxes
[quoted text clipped - 10 lines]
> Thanks,
> James

Reply to this Message

JamesJ - 13 Apr 2005 22:33 GMT

Thanks much, that did the trick. But, it left me with a couple more
questions.

1) Should I populate the list boxes from the OnOpen of the form or the
Row Sources?
2) Where might I find article(s) on decompiling?

Thanks again,
James

> James, I'm not really clear on this. I think you are saying that if you
> save the SQL statement in the RowSource property of the list boxes, then
[quoted text clipped - 56 lines]
>> Thanks,
>> James

Reply to this Message

Allen Browne - 14 Apr 2005 02:18 GMT

Whatever is easiest.

Personally I just set the RowSource property at design time, and only use
the programmatic if if needs to be reassigned depending on user-input.

Signature

Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

> Thanks much, that did the trick. But, it left me with a couple more
> questions.
[quoted text clipped - 66 lines]
>>> Thanks,
>>> James

Reply to this Message