jwcolby
jwcolby at colbyconsulting.com
Thu Aug 25 12:00:00 CDT 2011
Yep, this is that "some hidden code thing" happening in the editor. Not a ghost in the machine, but a ghost in Access. I am absolutely convinced that there is "invisible code" stuff that the editor puts in there, similar to the wordperfect "show codes" thing except that there is no "show codes" equivalent in the VBA editor. I first ran into this in the late 90s when I was tracking down a page fault. I found the line of code that was page faulting, nothing wrong with the syntax. Cut it to the paste buffer and the page fault went away. Pasted it back in and the page fault was still gone. There is something that cannot be seen, which does not survive the trip to the paste buffer and back. In fact this time I just commented out the line and the problem went away. I uncommented the line the problem was still gone. VBA has a JIT compiler that translates the english language stuff in the module into P-code. Something unseen was causing the JIT compiler to throw some kind of error. This is a very old bug in Access. Pretty toolbars! John W. Colby www.ColbyConsulting.com On 8/25/2011 11:44 AM, Tony Septav wrote: > Hey John > Not an answer but in a 2003 application a form all of a sudden would not > open, code crashed and up popped one of Access's cryptic error messages. > Checked the offending code everything looked fine, I could not see any > reason it should stop working. Ran my backup it worked fine. After mucking > around for awhile, I finally deleted all the code and copied and pasted the > code from my backup. Opened the application and everything worked fine. Had > one of those "go figure moments" and then just put it down to a ghost in the > machine. > Problem fixed but I have no idea why. > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Thursday, 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 > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 10.0.1392 / Virus Database: 1520/3855 - Release Date: 08/24/11 >