Breakpoint will not go away.

S

Stapes

Hi

I put a breakpoint before a line of code:

Private Sub Command58_Click()

so that when I clicked the button, I could see what was happening. A
wee brown spot appears in the margin next to the line of code. When I
ran it, I go to debug window - fine.
However, when I removed the breakpoint, it worked OK first time. Then,
I closed the database, re-opened it, and tried again. Once again, it
has opened on the debug window. No wee brown spots are visible. I have
tried pressing Remove All Breakpoints, and Compact & Repair Database,
all to no avail.

Help!

Stapes
 
A

Allen Browne

Typically this indicates that the 2 copies of the code are out of sync, so a
decompile fixes it.

Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

Then compact again.
 
M

Mr. B

Typically this indicates that the 2 copies of the code are out of sync, so a
decompile fixes it.

Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

Then compact again.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.









- Show quoted text -

In my experience, I have been able to resolve this type of issue by
simply adding a new dim statement somewhere in code.

Just go to any module and add: "Dim varNewVar " and then press enter.

Then immediately remove the new dim statement. (I know this sounds
stupid as a fix, but it is certainly worth a try, because it has
always work for me and it is simple and easy.) Doing this will cause
the Compile option to again become available. Make sure that all of
your breakpoints are removed and then save your changes and compile
your code.

That should resolve the problem.

If it does not then the suggestions by Arvin and Allen would certainly
be in order.

HTH

Mr. B
 
P

Pat Hartman \(MVP\)

I had this exact problem a couple of weeks ago. I couldn't get any of the
"normal" corruption recovery solutions to get rid of the problem so I
deleted the line that was causing the problem. Saved the form and then put
the line back.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top