Access 2003, break points not working

[Griff389]

Hi Guys,

i'm looking for some help in my access 2003 vba.

It seems that if I put break points (the red circle at the beginning of the line) in my code in order to debug something, they don't appear to break the code. When I reach where a break point should happen in the access form, I don't get taken back to the code. Instead the code just carries on running past the break point.

I also had an unfinished line of code in my form_current which should have errored when I changed records in the form. But this also didn't through up an exception like i'd have expected to.

Have I inadvertantly switched something off, or have I got a problem somwehre.

Regards

Griff

 

[Remou]

What happens if you add a message box to the code?

 

[Griff389]

It works fine.

I just tested by adding a new button to the form, adding these two lines of code:

MsgBox "test", vbOKOnly
MsgBox "test2", vbOKOnly

and putting a break point on each line.

When I clicked the button it just ran both message boxes, despite their being the two break points too.

 

[Griff389]

Incidently, this is on Vista, but I'm sure that's not the issue as I get the same results when test it on an XP Virtual machine too.

 

[Remou]

Put Stop st the very start of the sub, before anything else.

 

[Griff389]

I still get both message boxes firing instead of breaking.

     Private Sub Command17_Click()
     Stop

*    MsgBox "test", vbOKOnly
*    MsgBox "test2", vbOKOnly

     End Sub

(The * indicates the breakpoints)

 

[Remou]

In the code window, what is Tools->Options->General->Error Trapping set to? Can you compile? Have you done a compact & repair? Are any of your references marked MISSING? Have you tried a new, test database to see if that works?

 

[Griff389]

The error trapping is set to "Break on Unhandled Errors"

Yes compiling seems ok, and i've 'compact and repaired' it a few times.

Not sure on any references missing.

It definately seems to be something in the Database. I tried it with a different database (an old copy of the one i'm working on) and it breaks fine using the above example code.
Guess i'll have a trawl through the code and see if there's anything that jumps out.

I have been working between Access 2003 and Access 2007 but not sure if I actually edited this db in 2007.

Any other ideas are stll welcome of course.

 

[Remou]

You will find references under Tools->References.

 

[Griff389]

everything that is referenced is fine.

(cheers for the help by the way )

 

[Remou]

Try this:

http://www.granite.ab.ca/access/decompile.htm

And if it does not work, the best bet is probably to import to a fresh database before things get any worse.

 

[Griff389]

Thanks for the link. That didn't work either.
Looks like i'm going to import the forms into my old working copy along with any code I have changed, and see if that works.

 

[Remou]

A fresh, sparkling database is what is usually recommended.

 

[cadocs]

I bet that your Alt-F11 combination to open VB Editor doesn't work either. I just fixed my propblem by going to "tools" on the menu bar of Access, then to "startup", then you have to enable "use access special keys" and it should work. Let me know.