Error Checking & Break Point Failure

[Peter Hibbs]

I have a database (FE + BE) in A2000 which has suffered some
corruption (I think). The problem is that the Break Point facility no
longer works. I can enter a break point (the line goes brown) but when
the code executes the break point is ignored. Other databases on the
same hard disk seem to work OK.

So far I have done the following :-
Compiled the code, no errors shown.
Decompiled the database file.
Compacted and Repaired the file.
Tried the JETCOMP facility from MS.
Looked at Allen Browne's site but could not see anything relevant.

I have reverted to my back up copies from 1 and 2 weeks ago and the
error still persists so I'm thinking it is not a problem with the
database file itself. I even went back to the Windows Restore point of
3 days ago in case it was a Registry error, no difference.
The Error Trapping option is set to Break on All Errors, other options
are set to the normal default settings.

The other problem which may or may not be related (although it seemed
to happen at the same time) is that the Error Trapping does not work
at all. If an error occurs, instead of jumping to the error trapping
code it just tries to execute the error line. This problem seems to
affect all A2000 databases on the disk (although I haven't tested
every one yet).

It looks like Access itself is corrupted although these are the only
problems I've noticed so far. Am I looking at a re-install or is there
something else I can try first.

I have Access 2000 and Access 2003 installed so a complete re-install
would be a bit of a pain.

Anyone have any ideas what I should do next.

TIA

Peter Hibbs.

 

[Allen Browne]

In the code window, choose Options on the Tools menu.
On the General tab, make sure Error Trapping is set to:
Break on Unhandled Errors

While you are there, make sure Compile On Demand is unchecked, as that can
corrupt the database.

If you are still stuck, you may be able to temporarily work around it by
adding the line:
Stop
instead of a breakpoint.

 

[Peter Hibbs]

Allen

The Break on Unhandled Errors option makes no difference and the
Compile On Demand option has always been unchecked.

I entered the Stop command in the code but this made no difference,
i.e. the code just executed as if it was not there.

Any other ideas.

Thanks.

Peter.

 

[Tom Wickerath]

Hi Peter,

In order for a break point to be honored, you must have the option "Use
Access Special Keys" enabled. This option is found under Tools | Startup. A
restart of Access is required if you find that this option was not enabled.

I'm not sure about the other issues you've mentioned, such as the Stop
statement not being honored, and the error trapping not working.


Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Peter Hibbs]

Hi Tom.

Yes, that fixed the Break Point problem. I can't think how that flag
got disabled but it was and break points now work.

Regarding the error trapping, I now think that is a different issue. I
am doing some more testing on another PC and am making some progress.
If I get stuck I will start another thread.

Thanks again for the help, yet another thing I will have to remember
to check.

Peter.