Re: Access errors that I don't understand

Tech-Archive recommends: Fix windows errors by optimizing your registry

While ACCESS at times may "remember" breakpoints that are put in the code
while a developer is debugging an application, it's not a common situation.
For those infrequent situations, I usually comment out the line of code
where the breakpoint is being remembered (may have to comment out more than
one line if a compiler error occurs from leaving out that one line),
compact/repair and compile the database, then close the database, then open
it again and uncomment out the line of code and compile again. Another way
is to decompile the database by using the "decompile" switch for starting
ACCESS.

However, a more likely situation would be one of these two things:
1) The VBE's options is set to "Break on all errors" instead of "Break
on all unhandled errors".
2) The code where the "break" occurs has no error handler to trap an
error.

Very hard to say what the real cause is because we have no idea of the code
that is running when the "break" occurs, etc.
--

Ken Snell
<MS ACCESS MVP>



"louise" <louise@xxxxxxxxxx> wrote in message
news:8bucg.1675$sb7.559@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Re Access 2003

I'm writing to this group because I really don't know where to post.

I have hired someone who states he Access Certified. I have used him
several years ago without problems. This time I have asked him to change
some reports in an existing database and a few other similar things.

I keep having problems with his database. He seems to do what I request
but then when I go to run reports, I frequently get debug errors. I have
complained and received the following response

"It seems that Access is stuck in going into Break mode. This is a common
bug in the Access Application. The fix is to compile the code and Compact
and Repair the file. "

Is this a "common bug" in the Access Application? Does his comment make
sense?

TIA

Louise


.

Relevant Pages

  • Re: Breakpoints in VBA (Opposite of below)
    ... "dymondjack" wrote in message ... Rather than having Breakpoints that do not respond, ... I compile the project without first removing all the bp's ... As for curing a case of phantom breakpoints, I've usually succeeded by modifying a line of code inconsequentially, then clicking Debug -> Clear All Breakpoints, then compiling the database, then clicking the Save button. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access xp - Why does debugger break in when I have no breakpoi
    ... >> can compile without it. ... Close the database. ... >> <MS ACCESS MVP> ... >>> no breakpoint set there - I've Cleared All Breakpoints from the Debug ...
    (microsoft.public.access.modulesdaovba)
  • Re: Break points HELP!!
    ... finished i cleared the breakpoints. ... everytime i open the database it breaks into the ... database, compact and repair, and see if that fixes it. ... Then open the database, compact it, open the VBA editor, compile, and compact ...
    (microsoft.public.access.formscoding)
  • Re: Access xp - Why does debugger break in when I have no breakpoint .
    ... VBE sometimes remembers "phantom" breakpoints. ... can compile without it. ... Close the database. ... > I've made a change to an app that's been running for years. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Me.ControlName = Something
    ... Steve, I think you will discover that my original diagnosis was probably correct, and that whatever is actually triggering the Form_BeforeUpdate event's firing is actually where the problem lies, not the Form_BeforeUpdate even itself. ... Compact the database to get rid of this junk: ... Still in the code window, choose Compile from the Debug menu. ... > Private Sub Form_BeforeUpdate ...
    (microsoft.public.access.formscoding)