Access ignores my request for a code break - why?

[ManningFan]

You know in the VBA Editor when you can click in the column to the
left of the code and you get that little red dot? Access is SUPPOSED
to break the code at that point so you can troubleshoot what you're
doing.

This works in all of my databases but one. Is there a switch
somewhere to turn it on, or is the database phuxored? Is there a way
to prevent this behavior? I've seen this happen before but I don't
think I've ever found a solution to it. Anyone got any ideas?

[Tom van Stiphout]

On 6 Apr 2007 06:27:47 -0700, "ManningFan" <ma********@gmail.com>
wrote:

I would /decompile that database, and if that did not help, export all
objects to text, and import in new db.

-Tom.

>You know in the VBA Editor when you can click in the column to the
left of the code and you get that little red dot? Access is SUPPOSED
to break the code at that point so you can troubleshoot what you're
doing.

This works in all of my databases but one. Is there a switch
somewhere to turn it on, or is the database phuxored? Is there a way
to prevent this behavior? I've seen this happen before but I don't
think I've ever found a solution to it. Anyone got any ideas?

[RoyVidar]

"ManningFan" <ma********@gmail.comwrote in message
<11*********************@o5g2000hsb.googlegroups.c om>:

You know in the VBA Editor when you can click in the column to the
left of the code and you get that little red dot? Access is SUPPOSED
to break the code at that point so you can troubleshoot what you're
doing.

This works in all of my databases but one. Is there a switch
somewhere to turn it on, or is the database phuxored? Is there a way
to prevent this behavior? I've seen this happen before but I don't
think I've ever found a solution to it. Anyone got any ideas?

Been playing with the database properties, have we? In particular the
Use Access Special Keys from Tools | Startup? When unchecking that
setting, I think also the AllowBreakIntoCode property is also set to
false in some versions.

Try checking the special key thingie, close and reopen, or if necessary
do something along the lines of the following air code

with currentdb
.Properties("AllowSpecialKeys") = true
.Properties("AllowBreakIntoCode") = true
end with

--
Roy-Vidar

[ManningFan]

On Apr 6, 1:44 pm, RoyVidar <[e-mail]:

"ManningFan" <[e-mail] in message

<[e-mail].c om>:

You know in the VBA Editor when you can click in the column to the
left of the code and you get that little red dot? Access is SUPPOSED
to break the code at that point so you can troubleshoot what you're
doing.

This works in all of my databases but one. Is there a switch
somewhere to turn it on, or is the database phuxored? Is there a way
to prevent this behavior? I've seen this happen before but I don't
think I've ever found a solution to it. Anyone got any ideas?

Been playing with the database properties, have we? In particular the
Use Access Special Keys from Tools | Startup? When unchecking that
setting, I think also the AllowBreakIntoCode property is also set to
false in some versions.

Try checking the special key thingie, close and reopen, or if necessary
do something along the lines of the following air code

with currentdb
.Properties("AllowSpecialKeys") = true
.Properties("AllowBreakIntoCode") = true
end with

--
Roy-Vidar

You are a GOD among insects, Roy-Vidar. I must have unchecked it and
not realized what I was doing.

[Tom van Stiphout]

On Fri, 06 Apr 2007 19:44:50 +0200, RoyVidar
<ro*************@yahoo.nowrote:

Good call, Roy!
Never underestimate the !@#$%^ some people will get themselves in by
going where they shouldn't.

-Tom.

>"ManningFan" <ma********@gmail.comwrote in message
<11*********************@o5g2000hsb.googlegroups. com>:

>You know in the VBA Editor when you can click in the column to the
left of the code and you get that little red dot? Access is SUPPOSED
to break the code at that point so you can troubleshoot what you're
doing.

This works in all of my databases but one. Is there a switch
somewhere to turn it on, or is the database phuxored? Is there a way
to prevent this behavior? I've seen this happen before but I don't
think I've ever found a solution to it. Anyone got any ideas?

Been playing with the database properties, have we? In particular the
Use Access Special Keys from Tools | Startup? When unchecking that
setting, I think also the AllowBreakIntoCode property is also set to
false in some versions.

Try checking the special key thingie, close and reopen, or if necessary
do something along the lines of the following air code

with currentdb
.Properties("AllowSpecialKeys") = true
.Properties("AllowBreakIntoCode") = true
end with