MartyConnelly
martyconnelly at shaw.ca
Fri Nov 18 12:33:42 CST 2005
This assumes you have a timer event that starts running in say a hidden form on entry to the mdb Or if you are debugging put in the on open event of a form that has a timer This line Application.Modules.Count Checks if you have a vba module open in edit or debug mode Not sure if it is set to greater than zero if code behind a form is open If edit or debug in effect resets timer interval to zero John Colby wrote: >Where do you put this? It the timer event so that as it runs it checks >every time, and if encountered, shuts them all down? Or just in a button >somewhere? > >John W. Colby >www.ColbyConsulting.com > >Contribute your unused CPU cycles to a good cause: >http://folding.stanford.edu/ > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly >Sent: Friday, November 18, 2005 12:34 PM >To: Access Developers discussion and problem solving >Subject: Re: [AccessD] Syntax Corrections > > >Here is some code I got from Trevor Best that gets you around this >debugging problem >where you could get clobbered p-code > > you have a form that's open for the duration of the application with a >timer event, then put this code into it. >--- begin code --- > If Application.Modules.Count Then > Debug.Print "" > Debug.Print "*******************************" > Debug.Print "*** Turning off form timers ***" > Debug.Print "*******************************" > For Each frm In Application.Forms > Debug.Print frm.Name > frm.TimerInterval = 0 > Next > Debug.Print "*******************************" > Debug.Print "*** Form Timers turned off ***" > Debug.Print "*******************************" > Set frm = Nothing > > > End If >--- end code --- > > > >John Colby wrote: > > > >>I run into this when a form is open and firing the timer event. The >>timer event (and code) running causes an attempted compile of the code >>I am working on and the compile process does weird things. >> >>John W. Colby >>www.ColbyConsulting.com >> >>Contribute your unused CPU cycles to a good cause: >>http://folding.stanford.edu/ >> >>-----Original Message----- >>From: accessd-bounces at databaseadvisors.com >>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey >>Sent: Friday, November 18, 2005 9:45 AM >>To: Access Developers discussion and problem solving >>Subject: [AccessD] Syntax Corrections >> >> >>Ok I've put up with it for a while but this is driving me nuts now. >> >>Access 97. This has started fairly recently and I'm not aware of having >>changed any setting to cause it. What it is is that as I type code >>Access will, on occasions, 'correct' it as I type. Let me give you an >>example. >> >>I type: >> >>strA=strA & " >> >>I haven't finished the line but sometimes (and always if I hesitate >>long >>enough) Access will automagically add spaces either side of the = for me >> >> >and > > >>a second " so that what I now have is >> >>strA = strA & "" >> >>Now that's ok except that while 3 characters have thus been added to >>the line the cursor hasn't moved. Instead, therefore, of being at the >>end of the line it's now 3 spaces before the end (immediately after the >>& in my example). If I'm not looking at the screen and keep typing my >>text then when I do eventually look up, or just hit enter at what I >>think is my line end, the statement is shot to pieces. >> >>I've tried unchecking various Options (eg Auto Syntax Check) but I >>can't seem to stop it. I swear that what used to happen was that this >>tidying up occurred only when I hit Enter at the end of a line. Doing >>it while I'm still typing the line is doing my head in. >> >>Does anyone know how I switch this behaviour off? >>-- >>Andy Lacey >>http://www.minstersystems.co.uk >> >> >>________________________________________________ >>Message sent using UebiMiau 2.7.2 >> >> >> >> >> > > > -- Marty Connelly Victoria, B.C. Canada