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

Create MDE causes Access to crash

P: n/a
Hello,

Is it possible to step through the "Create MDE" process and see what is
causing Access to crash?

I tried, unsuccessfully, many times to create an MDE from my database.
But, randomly, I checked the "Allow Full Menus" in the Startup section.
I was then able to create an MDE.

That worked once. It has not worked since and I don't particularly
want to have the menus enabled.

On a related note (perhaps)...

I was out of the office for a week and asked a colleague to manage the
database. Basically, compact when necessary. When showing them how,
Access crashed, mid-compact. Thinking this may be an issue with their
particular machine, I asked another colleague. The same thing happened.

Am I going bonkers?

Feb 23 '06 #1
Share this Question
Share on Google+
9 Replies


P: n/a
The problems you are experiencing indicate that there is some kind of
corruption in this database.

My first guess would be either Name AutoCorrect, or a decompile, but the
problem could actually be caused by your hardware, software, patches,
network, users, or development practices.

For a list of the things to work through to get a stable database, see:
Preventing corruption
at:
http://allenbrowne.com/ser-25.html

--
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.

"badboybrown" <se*****@gmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
Hello,

Is it possible to step through the "Create MDE" process and see what is
causing Access to crash?

I tried, unsuccessfully, many times to create an MDE from my database.
But, randomly, I checked the "Allow Full Menus" in the Startup section.
I was then able to create an MDE.

That worked once. It has not worked since and I don't particularly
want to have the menus enabled.

On a related note (perhaps)...

I was out of the office for a week and asked a colleague to manage the
database. Basically, compact when necessary. When showing them how,
Access crashed, mid-compact. Thinking this may be an issue with their
particular machine, I asked another colleague. The same thing happened.

Am I going bonkers?

Feb 23 '06 #2

P: n/a
Jay
I had a similar issue and the reason was a corrupted report. Spotting
which report was corrupted was the hard part because I do not know of
any way of accomplishing this task.

However, fixing it is easy. Simply copy the corrupted report and paste
it. Delete the old report and change the name of the new one to the
name of the corrupted one. Unless someone else knows a way of spotting
the corrupt report, you must do this for all of your reports. You
should do the same for your forms as I have had forms crash Access
simply by opening them.

Btw, I should note that the crashes only occur when developing and
never on the finished product. Not sure how a report or form become
corrupt in the first place, but the fix is easy at least.
badboybrown wrote:
Hello,

Is it possible to step through the "Create MDE" process and see what is
causing Access to crash?

I tried, unsuccessfully, many times to create an MDE from my database.
But, randomly, I checked the "Allow Full Menus" in the Startup section.
I was then able to create an MDE.

That worked once. It has not worked since and I don't particularly
want to have the menus enabled.

On a related note (perhaps)...

I was out of the office for a week and asked a colleague to manage the
database. Basically, compact when necessary. When showing them how,
Access crashed, mid-compact. Thinking this may be an issue with their
particular machine, I asked another colleague. The same thing happened.

Am I going bonkers?


Feb 23 '06 #3

P: n/a
To discover which report(s) are corrupted, create a new database and import
them. Watch the names: where the import fails, the report is corrupt.

--
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.

"Jay" <jm*******************@yahoo.com> wrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...
I had a similar issue and the reason was a corrupted report. Spotting
which report was corrupted was the hard part because I do not know of
any way of accomplishing this task.

However, fixing it is easy. Simply copy the corrupted report and paste
it. Delete the old report and change the name of the new one to the
name of the corrupted one. Unless someone else knows a way of spotting
the corrupt report, you must do this for all of your reports. You
should do the same for your forms as I have had forms crash Access
simply by opening them.

Btw, I should note that the crashes only occur when developing and
never on the finished product. Not sure how a report or form become
corrupt in the first place, but the fix is easy at least.
badboybrown wrote:
Hello,

Is it possible to step through the "Create MDE" process and see what is
causing Access to crash?

I tried, unsuccessfully, many times to create an MDE from my database.
But, randomly, I checked the "Allow Full Menus" in the Startup section.
I was then able to create an MDE.

That worked once. It has not worked since and I don't particularly
want to have the menus enabled.

On a related note (perhaps)...

I was out of the office for a week and asked a colleague to manage the
database. Basically, compact when necessary. When showing them how,
Access crashed, mid-compact. Thinking this may be an issue with their
particular machine, I asked another colleague. The same thing happened.

Am I going bonkers?

Feb 23 '06 #4

P: n/a
Jay
Thanks Allen.

Feb 23 '06 #5

P: n/a
Thanks guys!

I'll spend some more time investigating this.

Feb 23 '06 #6

P: n/a
I think I've cracked it...

- I've been using the Tools | Startup menu to nominate the form on
startup and hide the menus and toolbars.

- To get around this I hold down the "Shift" key when opening the
database to do any design work. This seems to override the Startup menu
options.

- By only setting the "Startup" options just before creating the .mde
(i.e. The options weren't set, therefore I did not have to hold the
"Shift" key when opening the database), everything runs smoothly.

- I have to close down Access and reset the Startup menu options
afterwards, but it's not a biggy.

So now for the questions.

1.) Is holding down the "Shift" key a bad thing to do? I was taught it
in my first Access Training course.
2.) Does it do more than override the Startup menu?
3.) Is there a better way of doing things?

I thank you in advance for your patience.

Feb 23 '06 #7

P: n/a
"badboybrown" <se*****@gmail.com> wrote in
news:11********************@g47g2000cwa.googlegrou ps.com:
1.) Is holding down the "Shift" key a bad thing to do? I was
taught it in my first Access Training course.


That has nothing whatsoever to do with the MDE problem. I can't even
conceive of a relationship.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Feb 23 '06 #8

P: n/a
Holding down Shift bypasses the AutoExec macro as well as the startup
options, leaving you with the default menus and toolbars and the Database
window. There are no bad side-effects, unless you were relying on some
startup code to run.

You might want to try holding down the Shift key while you compact the
database, so that when it restarts your startup code does NOT run. If your
startup code is the culprit, you might find that this lets you create the
MDE. If it does, there is something wrong with whatever code runs
automatically (e.g. form AutoExec, or the Open/Load events of the startup
form.)

--
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.

"badboybrown" <se*****@gmail.com> wrote in message
news:11********************@g47g2000cwa.googlegrou ps.com...
I think I've cracked it...

- I've been using the Tools | Startup menu to nominate the form on
startup and hide the menus and toolbars.

- To get around this I hold down the "Shift" key when opening the
database to do any design work. This seems to override the Startup menu
options.

- By only setting the "Startup" options just before creating the .mde
(i.e. The options weren't set, therefore I did not have to hold the
"Shift" key when opening the database), everything runs smoothly.

- I have to close down Access and reset the Startup menu options
afterwards, but it's not a biggy.

So now for the questions.

1.) Is holding down the "Shift" key a bad thing to do? I was taught it
in my first Access Training course.
2.) Does it do more than override the Startup menu?
3.) Is there a better way of doing things?

I thank you in advance for your patience.

Feb 24 '06 #9

P: n/a
> You might want to try holding down the Shift key while you compact the
database, so that when it restarts your startup code does NOT run. If your
startup code is the culprit, you might find that this lets you create the
MDE. If it does, there is something wrong with whatever code runs
automatically (e.g. form AutoExec, or the Open/Load events of the startup
form.)


I didn't realise you could do this. Duh.

I've imported all the objects into a new database, decompiled and
compiled and saved and it works both ways now.

Thanks again for your help

Feb 24 '06 #10

This discussion thread is closed

Replies have been disabled for this discussion.