I have an Access app. that will not react to any breakpoints I place in the form code. It will not even stop on a debug.print. It is Access 2k using DAO 3.6. I'd really like to be able to run some forms/code thru the debugger. Any ideas as to why the debugger does not work?

May sound silly but....could the reason be b/c I'm trying to use Access XP when looking at the code? Although, my co-worker has the same issue and she has Access 2k.

Any help is appreciated.

Thanks..

Can't say for sure without knowing what event, (and possibly seeing your
code,) however, there are a few form events that can't be single stepped.
(And don't ask me which ones. :-)

I'm curious about your comment about Debug.Print. It is not supposed to stop
the code. However, you should see something printed in the immediate window.

You can use Debug.Assert to stop code, however, you'll probably still have
the same problem you're having with break points.

In those cases where I've had this happen, I copy the code into a standalone
module and single step it there. Although there are some cases where you
have to have the code in the event for state issues, you can usually work
around it.

Good luck.

Sco

"arv" <(E-Mail Removed)> wrote in message
news:782C7CDD-946D-45F3-846F-(E-Mail Removed)...
> I have an Access app. that will not react to any breakpoints I place in
the form code. It will not even stop on a debug.print. It is Access 2k
using DAO 3.6. I'd really like to be able to run some forms/code thru the
debugger. Any ideas as to why the debugger does not work?
>
> May sound silly but....could the reason be b/c I'm trying to use Access XP
when looking at the code? Although, my co-worker has the same issue and she
has Access 2k.
>
> Any help is appreciated.
>
> Thanks..