[AccessD] How to troubleshoot

Well, your problem was replicable - my Access just tells me it's stopped
working at random times. :(

R

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: August 25, 2011 5:09 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] How to troubleshoot

Rocky,

In my case I am developing in Access 2003 but running it under 2007 runtime
so that I can distribute it for free.  The application ran everywhere except
under runtime.  The application was running, even under runtime, and then
something occurred in a version about a month ago and it stopped running
under runtime, returning that error message.  It still ran under the dev
environment. 
Another application I built was still running under runtime, so it is not
the runtime install.

I found the latest version that still ran under runtime and started
comparing the startup code. 
Basically the "bad" version was failing even before my little security log
in form opened.

There is an Init() function with about 8 functions which init() calls and I
decided to start at the very end and comment out line by line until the db
opened.  The very last line in Init() opened the switchboard.  That line
cannot even run until the log in occurs, however when I commented out that
last line (open switchboard) the database opened under runtime and allowed
me to log in, although it didn't open the switchboard after the log in (of
course).

Hmmmm... a line of code not even reached is preventing the database from
even opening.

I uncommented that line and it still runs under runtime.  Hmm....

Problem solved, but what was the problem?

I had done a complete decompile / compile / compact cycle and that did not
solve the problem, but commenting and uncommenting a line that is not even
executed until after log in allows the database to open, let me log in and
open the switchboard.

John W. Colby
www.ColbyConsulting.com

On 8/25/2011 12:23 AM, Rocky Smolin wrote:
> Don't know but I'm getting that "has stopped working" in 2003 in both 
> Access and Outlook (don't use word or excel much but they may have the 
> same
> problem) - Access in mdbs, Outlook when I'm writing an email.  Don't 
> know what to do about it.
>
> Rocky
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: August 24, 2011 7:19 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] How to troubleshoot
>
> Any clue how to troubleshoot "Access has stopped working" in the 2007 
> runtime?  I have a version that works just fine, and another app works 
> just fine but the latest version just immediately closes giving that 
> error message.  "A problem sending a command to the program".
>
> --
> John W. Colby
> www.ColbyConsulting.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com