By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,376 Members | 3,024 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,376 IT Pros & Developers. It's quick & easy.

Breakpoint being hit even when THERE ARE NO BREAKPOINTS set

P: n/a
Hi. I am developing a database with Microsoft Access. When I run the
application I get flipped into debug mode in the Visual Basic window at
an old (unset breakpoint). I keep going to the Debug Menu and clearing
all breakpoints, even though there are no breakpoints currently set.
Yet, it still stops at the same location.

Any ideas?

I am running Access 2k3, but the database has been created to run on
Access 2k.

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Nov 13 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
I had the same problem with access97 last week...
I used the /decompile switch after saving a copy of the mdb
recompiled - everything now works fine

Susan Bricker wrote:
Hi. I am developing a database with Microsoft Access. When I run the
application I get flipped into debug mode in the Visual Basic window at
an old (unset breakpoint). I keep going to the Debug Menu and clearing
all breakpoints, even though there are no breakpoints currently set.
Yet, it still stops at the same location.

Any ideas?

I am running Access 2k3, but the database has been created to run on
Access 2k.

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***


Nov 13 '05 #2

P: n/a
This is a form of corruption that happens in Access projects from time to
time. You may need to decompile the project using the /decompile command line
switch.

On Tue, 28 Jun 2005 03:08:01 GMT, Susan Bricker <sl*****@verizon.net> wrote:
Hi. I am developing a database with Microsoft Access. When I run the
application I get flipped into debug mode in the Visual Basic window at
an old (unset breakpoint). I keep going to the Debug Menu and clearing
all breakpoints, even though there are no breakpoints currently set.
Yet, it still stops at the same location.

Any ideas?

I am running Access 2k3, but the database has been created to run on
Access 2k.

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***


Nov 13 '05 #3

P: n/a
Susan Bricker wrote:
Hi. I am developing a database with Microsoft Access. When I run the
application I get flipped into debug mode in the Visual Basic window at
an old (unset breakpoint). I keep going to the Debug Menu and clearing
all breakpoints, even though there are no breakpoints currently set.
Yet, it still stops at the same location.

Any ideas?

I am running Access 2k3, but the database has been created to run on
Access 2k.


Set a breakpoint. Then Ctrl+Shift+F9 - clear all breakpoints.

--
[OO=00=OO]
Nov 13 '05 #4

P: n/a
Steve Jorgensen <no****@nospam.nospam> wrote in
news:et********************************@4ax.com:
This is a form of corruption that happens in Access projects from
time to time. You may need to decompile the project using the
/decompile command line switch.


It's also an indication that you should probably turn off COMPILE ON
DEMAND and compile manually instead.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #5

P: n/a
On Tue, 28 Jun 2005 15:42:35 GMT, "David W. Fenton"
<dX********@bway.net.invalid> wrote:
Steve Jorgensen <no****@nospam.nospam> wrote in
news:et********************************@4ax.com :
This is a form of corruption that happens in Access projects from
time to time. You may need to decompile the project using the
/decompile command line switch.


It's also an indication that you should probably turn off COMPILE ON
DEMAND and compile manually instead.


Wow - I didn't even know about that option. I'll give that a try myself.
Nov 13 '05 #6

P: n/a
Steve Jorgensen <no****@nospam.nospam> wrote in
news:gg********************************@4ax.com:
On Tue, 28 Jun 2005 15:42:35 GMT, "David W. Fenton"
<dX********@bway.net.invalid> wrote:
Steve Jorgensen <no****@nospam.nospam> wrote in
news:et********************************@4ax.co m:
This is a form of corruption that happens in Access projects
from time to time. You may need to decompile the project using
the /decompile command line switch.


It's also an indication that you should probably turn off COMPILE
ON DEMAND and compile manually instead.


Wow - I didn't even know about that option. I'll give that a try
myself.


I was going to say that you needed to go back and read MichKa's
article on decompile:

http://trigeminal.com/usenet/usenet004.asp

but then I checked it and see it says nothing about compile on
demand.

I suspect this was a piece of MichKa advice.

I've had insignificant corruption since I started turning it off on
all my development boxes.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.