A2K7 RT stops working

[Stanley L.]

I have an app that runs fine as an ACCDB. I have RT on my PC that runs other
apps just fine. When I change the extension of this app from ACCDB to ACCDR
and run it, I get the message "Microsoft Access has stopped working". The app
hangs up on the auto-start splash screen. Observations are: (1) I have
verified that all routines have error handling; (2) I exported the startup
screen to a separate ACCDR and it ran fine; (3) The app compiles with no
problem and can make an ACCDE file that runs fine but will not run as an
ACCDR in RT (4) I have verified that the RT file is the latest version -
12.0.6304.500; (5) After a RT failure my desktop shortcut for Access no
longer functions and I have to go to MSACCESS.EXE and open it a couple of
times to get AC2007 functioning again; (6) All my menus are custom menus that
are presented when needed e.g. a report preview ribbon.

Can anyone tell me what is happening and how to rectify the situation. By
the way, when the "Microsoft Access has stopped working" message appears, it
says that MS will advise of a solution if one is known. There has been no
response re this.

Any help will be appreciated.

Stanley L.

 

[emmanuelle longbois]

I have an app that runs fine as an ACCDB. I have RT on my PC that runs
other
apps just fine. When I change the extension of this app from ACCDB to
ACCDR
and run it, I get the message "Microsoft Access has stopped working". The
app
hangs up on the auto-start splash screen. Observations are: (1) I have
verified that all routines have error handling; (2) I exported the startup
screen to a separate ACCDR and it ran fine; (3) The app compiles with no
problem and can make an ACCDE file that runs fine but will not run as an
ACCDR in RT (4) I have verified that the RT file is the latest version -
12.0.6304.500; (5) After a RT failure my desktop shortcut for Access no
longer functions and I have to go to MSACCESS.EXE and open it a couple of
times to get AC2007 functioning again; (6) All my menus are custom menus
that
are presented when needed e.g. a report preview ribbon.

Can anyone tell me what is happening and how to rectify the situation. By
the way, when the "Microsoft Access has stopped working" message appears,
it
says that MS will advise of a solution if one is known. There has been no
response re this.

Any help will be appreciated.

Stanley L.

 

[Albert D. Kallal]

I at a loss as to why it would not work.....

(5) After a RT failure my desktop shortcut for Access no

longer functions and I have to go to MSACCESS.EXE and open it a couple of
times to get AC2007 functioning again;

You taking about your development box..right? In this case after a failure I
would launch the task manager, and checked if a copy of access is still
running. If yes, you might want to kill it.

And, if this test is with a accDB, and not a true accDE, then I would
consider doing a de-compile and then a compact repair, and then re-compile
the code during your testing phase.

So, on your dev machine, I would simply start putting some msg box commands
in your startup code to try and determine where it stops.

In other words, does the main "startup" form load? What kind code do you
have for the startup of the applicaton?

So, start by making your first line of code:

msgbox "first line, press ok"

If that works, then you start placing msgbox commands farther and farther
into your startup code.

This should allow you to determine where you application is stopping.

Note that if you use a accDE, then you don't really need much error
handling.
Error trapping is a good thing but I always use a accDE since that does not
shutdown the runtime when you have an unhandled vba code error.

Anyway, the placing of msgbox commands farther and farther into your startup
code on your development box is an debugging approach that should allow you
to narrow down where the application is stopping or hanging up ms-access.

 

[Stanley L.]

Thanks. I hadn't mentioned it but I did /decompile the accdb and tried again.
There was no change. Once before I was getting that message when trying to
run an ACCDB file.In that case the /decompile did solve the problem.

Your 'message box' suggestion is a good trouble shooting approach and I will
use it. I will advise the results here when done. Thanks again.
Stanley L.

 

[Stanley L.]

Continuing trouble-shooting report
MS Office Diagonistics was run and it made one repair that may improve
stability. Running of the ACCDR after the repair produced no
changes....Access still crashes. The saga continues.
Stanley L.

 

[Stanley L.]

I found this command that brings up the 'Linked table manager' in an ACCDB
file but the very same command in RT causes A2K7 to crash. Even the error
processing does not prevent RT from crashing.The command is DoCmd.RunCommand
acCmdLinkedTableManager. Why ?

Is there another command that will bring up the linked Table Manager?

 

[Stanley L.]

A number of ACCDBs run fine and also I have a small ACCDB and ACCDE app that
runs fine in normal as well as RT. I believe there is some code that RT
chokes on and crashes. I found one as reported below but there are more code
instances. My trouble shooting is progressing but its a lot of work importing
and checking each form. It is too bad when code runs fine in a normal run but
hangs up only in the RT. Also it is too bad when error processing doesn't
advise before the RT crashes. Something is amiss because thatis the function
of error processing.

Thanks for your interest and help.
Stanley L