Jim Dettman
jimdettman at verizon.net
Wed Aug 17 09:37:07 CDT 2011
VBA keeps two copies of your code; source and compiled p-code. Source is what you see in the editor, compiled p-code is what actually gets executed. Very often, the two will get out of synch and that has been true ever since we switched to VBA in Access. Hard to say where the fault lies; Access in keeping the VBA project in LVP's in JET, or within VBA itself, but in either case, you can often get weirdness like this. A import into a fresh DB container will clear it up, as only source code is imported. /Decompile will often straighten it out as well, which invalidates all existing p-code, forcing a compile of the source. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Wednesday, August 17, 2011 09:27 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access 2007 - The story so far. And the real answer is (probably) - Access modules consist of what you see and what you don't see. Kind of like Word documents except that there is no "show codes" for access editor. I have seen exactly what you are discussing, and it has nothing to do with the error handler per se, it can occur on any line of code. I was tracing a page fault one time, stepping through code until the offending line caused the page fault. Perfectly valid code. I ended up cutting the line out and pasting it back in and the problem was gone. So there is some "invisible stuff" going on with the editor. cutting the offending "whatever" out causes that offending stuff to be corrected and you are back in business. BTW this is not 2007 specific, I was getting this back in 2K. I doubt it has ever been fixed. The dev team had too many pretty tool bars to work on to fix real bugs. John W. Colby www.ColbyConsulting.com On 8/17/2011 12:16 AM, Darryl Collins wrote: > Hehehehe, WTF indeed - I will keep that lill answer as my corporate back up > response in case someone get offended. I like it. > > Yeah, I was really surprised when that happened. I mean, I really was like > "What??". I don't think I have ever had code that runs to the error handler > (and I repeated the launch several times to check it happened consistently) > then run without ANY error once the "On Error Goto x" were commented out. > It has always just stopped at the offending line of code - And I mean > always!! > > My next thought was, hell, the error handler must be causing the issue, but > no - putting it back in had no impact at all. It is behaving nicely now > which is a good result I guess, but even so, really rather weird... > > Probably just blah blah to some of you, but I needed to tell someone and the > wife does care that much about the strangeness of code performance. > > Cheers > Darryl. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Benson > (VBACreations.Com) > Sent: Wednesday, 17 August 2011 12:41 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Access 2007 - The story so far. > > WTF = "Why'd That Fail?" ... we all know our acronyms. > > > Could this be vindication of my strategy of using no error handling? > > > (Apologies to Emilia and others who have tried to reform me for such a > paltry joke). > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins > Sent: Tuesday, August 16, 2011 10:28 PM > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] Access 2007 - The story so far. > > Well I have been trying to find something nice to say about A2007, and I > guess one thing is in form design view when you have all the controls > grouped and you expand or contract one of them, the rest move along in sync, > that is nice and can save a fair bit of time tweaking the form layout etc. > > Sadly, it doesn't make up for the rest of the bugs and nonsense I have come > across, but hey, it is something at least :) > > Latest weirdness was I had a file whose ADO connection string to the > back-end was failing. No idea why as it was working great on other PC's, so > I took the error handlers off the all the code so I could see exactly which > line was failing. Ran the code and it worked perfectly, WTF?? I mean, I > didn't put in an "On error resume next" I took out ALL the error handling > functions so it would go splat at the first problem, but instead it work > flawlessly first time. > > So I put back in the error handlers to see what might happen - maybe they > were causing the error somehow (although it was compiling just fine), and it > worked flawlessly again. > > Go figure. I fixed the problem, but no idea what happened or why that would > fix the issue.... > > Many instances of this sort of weirdness. If you are just mashing data > A2007 works mostly ok, but to develop an app in A2003 is far more stable and > easy to use. > > Approach with some caution if you can. > > Just me thoughts > Cheers > Darryl. > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com