This action will reset the current code in break mode

[TarponZeke]

I have an application taht has been deployed at several customers for 2+ years.

It is written in Access 2000 front end with a primarily access 2000 back end
but it does link to some sql tables for certain data.

I have a report in this application that is pretty complex. It runs about 5
or 6 different queries to massage the data to be what I want and then it
pulls the report.

The report is a pretty standard report with a subreport on it. no big deal
there.

About a month or two ago, one of the clients called and said whenever they
run the report, it comes up on the screen fine. When they go to close the
report it gives the error: "This action will reset the current code in break
mode. Do you want to continue? Yes or No".

If you click yes, it just pops the error back up. If you click no, it just
goes back to the report preview.

The only way out of this is to end task. Not a very nice solution for your
customer.

I just logged into another client that has the same report and they are
getting the same error now as well.

I have tried everything I can think of to resolve this including writing
everything from scratch and it still comes up. I haven't been able to find
anything really helpful on the web although there were a couple articles out
there with that same error but no real resolution, or at least not one that
worked for me.

Any clue on what the heck is going on here and how I can possibly fix it? I
upgraded the one client to SP3 and that did not make a difference.

Any help would be greatly appreciated.

 

[Ofer]

In the report, check the code you have, sometimes in the error capture
somebody might have forgetten the resume without to continue to the Exit, and
that can cause a loop incase of an error.

e.g
Error_Stop:
msgbox error
resume ' Sub_Exit

Fix it to
Error_Stop:
msgbox error
resume Sub_Exit

Now, that might give you the solution to the loop but not to the error.
===============================================
To solve the problem, run the mdb, when you get the error message press
ctrl+Break and then select yes or no, to see where the error occur.

 

[TarponZeke]

Thanks for the reply but that is not the problem.

The only code in the report is a docmd.maximize in the on open and a
docmd.restore in the on close events.

This is some sort of corruption or something but I don't know what. It
worked for over 2 years and all of a suddent is giving this error.

Anyone else with any dieas?

 

[TarponZeke]

Turns out, I re-wrote the report and instead of using a subreport, I made it
a single report and I no longer get the error.

The subreport had a rather strange link child and link master relationship.
It was a concatenated string that I built in the queries to get the data like
I wanted it.

Evidently for some reason, that freaked it out and caused the error. I made
it a normal old report and grouped by my string field and put the data in the
detail section rather than having a subreport and everything is fine.

No clue why it all of a sudden stopped working though when it had been
working for months.