Mark A Matte
markamatte at hotmail.com
Wed Sep 24 09:48:27 CDT 2008
Rocky, Funny you should mention that...last night I was testing some code...and I was using breakpoints...before I left I stepped through...everything ok...and cleared each breakpoint (manually...not using the menu)...then a few minutes ago I opened up the same mdb and thought...lets watch my handywork from last night, and clicked a button...and it opened up to the line of code where the break used to be...I hit F5 and everything ok. I thought it was strange but it did not do it again. Is this a potential issue for distribution? Anyway to test/prevent/safeguard? Thanks, Mark A. Matte P.S...if you hadn't mentioned it...I might have thought I imagined it... > From: rockysmolin at bchacc.com > To: accessd at databaseadvisors.com > Date: Wed, 24 Sep 2008 06:54:15 -0700 > Subject: Re: [AccessD] Access 2002 - Another way to lose your work > > The one that kills me is the 'ghost' breakpoint. After doing the debugging > and clearing all the breakpoints, you send the app to the client, they run > it and suddenly it stops on a line where there used to be a breakpoint. > They hit F5 and everything carries on as normal. > > > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com > www.bchacc.com > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil > Salakhetdinov > Sent: Wednesday, September 24, 2008 6:17 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Access 2002 - Another way to lose your work > > <<< > Just another one of life's mysteries that Access throws at us. >>>> > Yes, and yet another "nice" feature is when you set a lot of breakpoints, do > quite some edits, debug for an hour or so, then push CTRL+S and get GPF.... > > This is why I also keep saving all the FE code into text files, or I usually > trying to make debugging/editing sessions very brief... - Test Driven > Development approach could help here to have very brief/none debugging > sessions although MS Access/VBA do not have(?) any frameworks for this > development method... > > -- > Shamil > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert > Sent: Wednesday, September 24, 2008 4:37 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Access 2002 - Another way to lose your work > > Hi Shamil, > > Actually the code modules and forms were all in the same front end. I do > have a library of code routines, but the front end is using the MDE version. > Just another one of life's mysteries that Access throws at us. > > Lambert > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil > Salakhetdinov > Sent: Wednesday, September 24, 2008 5:50 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Access 2002 - Another way to lose your work > > <<< > I still cannot figure out why the one object (a form) got saved, and all the > other changes (to code modules) got blown away. >>>> > Hi Lambert, > > My guess is that form belongs to your FE mdb, and modules were from library > mdb? > > Since MS Access 2000 AFAIKR (for sue that wasn't the case for MS Access 97) > if you debug/trace/edit your library mdb VBA code and try to save it then > you in fact save nothing... > > I always keep VBA code from mdb library modules copied and pasted and saved > manually in text code files and after I quit my debug session I do open text > files and copy over the code in VBA modules - well, I must say almost didn't > do that stupid work anymore as I'm mainly working with .NET - this "feature" > of getting VBA code from library MDB lost is one of the main "no-go" with > serious VBA code development anymore... > > To workaround the issue effectively (as MS is very probably not going to fix > that issue as VBA team doesn't exist there anymore or exists just to support > existing features AFAIU) - to workaround the issue effectively it would be > useful to have a COM add-in to be called by hot-key from VBA window to save > current (-ly opened) modules' code into text files, and have additional > feature to replace code in modules (including class/forms/reports modules of > course) from saved in text files... > > But beware! - when I did try to do something like that with MS Excel VBA > projects - I mean replacing code modules using text files - I did end up in > constant GPFing of MS Excel VBA projects - no workaround... > > For MS Access VBA - it usually works well but still one can get their mdb > broken - always keep a back-up copy in safe place when you do (mass) replace > of code in your VBA modules... > > -- > Shamil > -- > 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 > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com _________________________________________________________________ Get more out of the Web. Learn 10 hidden secrets of Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008