Code stops even though no break point set 1

[StumblingThrough]

I've got a Public Function inside a module that is triggered by an autoexec macro. For some reason, the execution of the code stops at the same line of code every time the application is opened, even though there is no breakpoint set there. When I press the StepOut button, execution continues as normal with absolutely no error messages. I've tried compiling the application, setting a break point at that line and then removing it, and execution still stops on that same line of code.

One additional point. When I create an .mde version, that version does NOT stop at that line of code.

Why is the .mdb database continually want to stop at this line of code? Thanks in advance.

 

[LittleSmudge]

This is a known intermittant bug in Access that somethins crops up when you leave a break point in the code when you save the .mdb


What you need to do is run 'Remove All Breakpoints' from the code window Debug menu and then do some other change in the code ( add and then delete a space char ) and resave the module.

THEN it forgets the old breakpoint.



'ope-that-'elps.

G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[StumblingThrough]

That did it, Smudge. Thanks!!