This action will reset the current code in break mode (1 Viewer)

[intern42]

I'm encountering a weird error in my Access db.

While debugging a form, I added a couple of message boxes.

Now, whenever I try to close an opened window, whether the window is a form that is "running," a table in design view, ANY window, I get the error message:

"This action will reset the current code in break mode.
Do you want to stop running code?

*To halt the execution of the progam so the Modual window can be closed, select Yes.
*To leave the code in the current state, select No."

If I select Yes, the error window remains on the screen.
If I select No, I'm still stuck with the opened windows.


Has anyone encountered anything like this before?

I am completely clueless.

 

[Fuga]

If I select Yes, the error window remains on the screen.

Do you mean that when you select "yes", nothing at all happens?

Fuga.

 

[intern42]

That is correct.

The error window flickers, as if it closes then immediately opens again, yet it always remains.

 

[Fuga]

Sounds strange. What happens if you quit the db?

 

[intern42]

Quitting the db wasn't possible...

The first time, I stopped Access by going into Task Manager and ending the task.

When the error window came up again, I tried shutting the Database window.

This caused the program to "hang up" and become unresposive.

A Windows message came up informing me that the program was unresponsive and I chose to end it.

Since then, the error has not occured again.

I'm currently testing the db and hope to never see it again.

 

[Fuga]

It might also be a good idea to repair and maybe compact the db. That sometimes takes care of trouble.

Fuga.

 

[Rich]

Have you compiled and saved all modules?

 

[intern42]

All my code is compiled and I have the db set to compact and repair on close.

This problem hasn't resurfaced and I'm hoping that it was just a random incident.

Thanks for the suggestions.

 

[rockman]

I've started having this error today. I've complied code and compacted the db and it is still occuring. I also have to perform an End Task via the Task Manager in order to get out of Access. Any help would be welcomed.

 

[AncientOne]

If this is a Modal form, have you tried ALT-F4 to close it?

 

[rockman]

Nope not a modal form.. but thanks for thinking about it.

 

[rockman]

In case it helps somebody in the future.

The "bug" described above kept happening. I created a new form and cut and pasted all of my controls from the buggy form to the new form (without any of the VBA code). The bug occurred in the new form.

I created a new form AND controls from scratch to match the buggy form. And the new form worked fine. I even cut and pasted the VBA code from the buggy form to the new form.

I have to conclude that one of the controls in the old form "contained" the bug. If this error happens to you, try recreating the form from scratch.

HTH

 

[stormin_norm]

I also had this error. I want to trap the error so my user doesn't need to run the task manager to stop access.

I have a form, the user fills in the criteria, clicks a button, opens a report. Problem is: I changed the field name of a linked table.
The form receives the 2766 error, traps it in the error handler, executes the "resume exit_".
Then I get the "The action will reset the current code in break module"

I can go back into design view of the form. But can't modify the table field value. I get a "you can't carry out this action" error.
I can only use taskmanager to stop access.

The form had controlBox=No, MinMax=No, Close=No
I reset these all to yes and tried it again. Same error.

The form, query & report were imported from A97 or A95.

I tried to recreate this in a2k. Access automatically changes the query to the changed table id name. If I delete a field name to force an error in report, or if there is nodata and I force a cancel=true in the report, the error handling on the form blasts the message and access continues okay. - Normal behavior

Therefore, Can we assume this only happens with imported A97/95 forms?
There is nothing on the access support page regarding this error.

 

[Pat Hartman]

Intern42,
Do you have a form with a timer event running? This causes strange debugging errors.

Norm,
I'm a little confused by your post. But, there is a bug with the name autocorrect feature. It doesn't seem to work, even if you specifically turn it on, for converted databases. The solution is to create a new A2K db and import all the objects. I think name autocorrect will then work properly. There are other bugs with this feature which may be fixed if you install service pack 3 for Office 2K.

 

[stormin_norm]

Pat-

You are probably right on the money with the autocorrect. This database was in 'beta' as A97 and then ported to A2k. I then imported what was 'worthwhile' into a new A2k db. So the error seems to have propogated between versions.
-norm.

 

[mcadle]

I had the exact same thing happen today on a db that has been running fine for over a year. The problem occured when the user clicked on a text box to open a new form. I found out that one record in the table had become corrupted. Any time I tried to view the table in spreadsheet view and scrolled down to where the record was I got that same error. It wouldn't go away. I finally was able to figure out which record it was and delete it then rebuild it. Funny...never had it happen before. Hopefully, just a one time deal.

 

[drb555]

I get this same error when running a specific query
which replaces some text on a form with some different text
It only occurs if there are more than 127 characters in the field

 

[drb555]

I get this same error when running a specific query
which replaces some text on a form with some different text
It only occurs if there are more than 127 characters in the field

just discovered that it only occurs when I was trying to update a field on a form. If I updated the table rather than the form there was no problem.