Step Into to debug does not work (1 Viewer)

warwica · Jun 14, 2007

I have a database that I created a while ago but for some reason when I try to run through code in step mode it does not work. Instead the entire code runs as if I'd hit Run. Also, although I can set break points in the code they are ignored and the code again just runs straight through.

I am now trying to make and tests some changes to the db but this is making it nigh on impossible!

Has anyone else come across this and if so what's the solution?

gemma-the-husky · Jun 14, 2007

are you sure the code is reaching the breakpoints?

i can't see any other reason for it not to respect the breakpoints

RuralGuy · Jun 14, 2007

Any chance you have a Timer event happening? That can cause some strange results such as you have described.

warwica · Jun 15, 2007

Yes the code is reaching the breakpoint. If I set a breakpoint before e.g. a message box statement it runs past the breakpoint and puts up the dialog box from the message box statement.

There are no Timer events running.

I do have a class module that I imported that runs a pop up calendar from a button on a form.

MsfStl · Jul 5, 2007

I am running into this same problem. I am modifying a program and want to test a control. The code runs through, ignoring the breakpoints. What may be causing this?

MsfStl · Jul 5, 2007

Ok, I
1) Added the code:
DoCmd.SetWarnings (-1)
Which turns the SetWarnings properties on.
2) Checked the Tools/Startup checkbox "Allow Special Keys"
3) Closed the program and restarted

One of those worked. But, I am unsure what I did for the program to run through the breakpoints in the first place. Does anyone have an idea as to what may have been the cause of the code running through the breakpoints? Fixing the problem the way I did resolves the issue, but it won't prevent me from making the mistake again, because I don't know what I did wrong in the first place.

Thanks for your time.

Scot

boblarson · Jul 5, 2007

It's possible you accidentally set yourself without warnings. I know I've been burned in the past by using DoCmd.SetWarnings False and then I didn't have the code to set it true in the error handler so that if it failed before getting to the part where it reset the warnings, I would then end up without any.

That's the one I would think would be the most likely.

RuralGuy · Jul 5, 2007

Scot,
I think it was this one:
2) Checked the Tools/Startup checkbox "Allow Special Keys"

boblarson · Jul 5, 2007

RuralGuy said:
Scot,
I think it was this one:
2) Checked the Tools/Startup checkbox "Allow Special Keys"

Yes, you are correct:

MsfStl · Jul 5, 2007

Yeah, I had clicked off everything on the original DB in the StartUp once I passed it on to the user (prevents them from getting inside, since they don't know the "Control" Key at startup) and now I am modifying a copy as a template for another project. It was driving me bananas trying to test my code, because I couldn't walk through it. Thanks guys. Learn something everyday!

Scot

Step Into to debug does not work (1 Viewer)

warwica

New member

gemma-the-husky

Super Moderator

RuralGuy

AWF VIP

warwica

New member

MsfStl

Registered User.

MsfStl

Registered User.

boblarson

Smeghead

RuralGuy

AWF VIP

boblarson

Smeghead

MsfStl

Registered User.

Similar threads

Users who are viewing this thread