Invisible Break Point?!?!?

[FBxiii]

I have got a strange occurance going on with a piece of code.

It functions as it should with no problems apart from it goes into the debug
window and execution stops on a certain line of code.

It is a recently added piece of code and I would of placed a breakpoint on
it. When the code goes into break mode, the breakpoint is not visible!!!

I know the simple solution is to press F5 to continue execution but one of
my colleagues gets worried when it happens.

I have tried Clearing All Breakpoints, etc but to no avail.

Can anyone help me?

Cheers,
Steve.

 

[Robert Morley]

I've seen this behaviour before as well, where a breakpoint seems to be
retained even though you removed it. Just decompile the database and
everything should be fine. To decompile, click Start, Run, then enter:

"full path to MSAccess.exe" /decompile "full path to your app"

Note, include the quotes as shown, and obviously substitute the appropriate
names.

(If you find yourself decompiling a lot, you may want to add the command to
the context menu for MDB's, ADP's, and the like.)


Rob

 

[FBxiii]

Rob,

Thanks for the reply but unfortunatley I am working on an XP network and do
not have administrators rights to use the Run command!

Is there an easier way?

Cheers,
Steve.

 

[Van T. Dinh]

1. Open any code module.
2. Type some blank characters at the end of a line of code / comment and
then move the cursor to another statement.
3. Use the Menu command Clear All Break Points.
4. Compile All
5. Save the module

The above steps should clear the phantom break point.

 

[david epsom dot com dot au]

Create a shortcut on your desktop.

I've seen networks that discard the desktop on login,
but I've yet to see a network that prevents you from
dropping stuff on your desk: it is part of a r/w
part of your user profile.

The shortcut should be to MSACCESS.exe (you can't just
drag an existing shortcut to Access - those are shortcuts
to the installation/file management system)

To find msaccess.exe, you probably can't browse directly
to c:\program files, but you probably can browse to
c:\program files\microsoft office

Just put the runcommand as below in the new shortcut.


(david)

 

[Terry]

This is a known problem that I have come across as well. I generally find
that it will be caused by having a break point set and using Debug |
Compile, this appears to set the break point in stone. Do this to get rid of
it:
1) At the line that the invisible break point stops, copy the line and paste
it immediately below itself.
2) Comment out the original line.
3) Ensure no other break points are set.
4) Debug | Compile the application.
5) Remove the commented out line of code.
6) Debug | Compile again.

The above causes Access to remove the invisible break point.

Regards

Terry

 

[FBxiii]

Thanks for all the good advice.

I did the Compact/Repair then compiled the code and it seems to of gone now.

Access 2003 has some wierd and wonderful ways........

Cheers,
Steve.