famous error with a twist

  • Thread starter Thread starter JAM
  • Start date Start date
J

JAM

This error is discussed in the newsgroups for the last 2
years. MS has a solution, but it doesn't work for me (see
below). Has anyone seen this?

Here is the error message when closing a table:

"this action will reset the current code in break mode".

See MS KB #304548 (this does not work for me)

Here are MORE DETAILS ... any help much appreciated!!

1. Access 2000 running on Windows 2000 Pro, and NT (NT is
the operating environment, 2000Pro is the development
environment). Error is the same on both.

All tables are local (no linked tables). Error appears
when I am the single user, with everything on one machine.

2. When copying, exporting table from, or importing a
table to another db, or copying rows from a table, the DB
locks up, or stops copying, and/or puts the db into a mode
where the table can't be closed. It gives the error:

"this action will reset the current code in break mode".

NOTE: ALL code has been deleted from the db and this
error still appears!

After this error appears, I can no longer copy or paste
records, and cannot close the table without clicking 'no'
on the dialog box noted above. Clicking 'yes' just brings
up the same dialog again over and over.

NOTE 2: MS KB article# 304548 covers this error. I have
tried to follow their resolution, but the resolution calls
for creating a new empty db and importing all of the
tables, queries etc. However, I cannot import from this
file: when importing, the import process stops and I am
left with an empty table. When I try to close the table
(the one I was importing TOO), I get the error noted above
("this action will...")

My searches have led me to believe I have either corrupted
data (one row is obviously corrupted, and I cannot delete
it), AND/OR there are records that are too long (but I
never get an error message saying that).

My goal is to copy the data to a fresh database and start
new. Any ideas would be greatly appreciated.

Thanks
Joe
 
You may very well have a corrupt database. However, first you should see if
the database will compile. That may show you some problems that exist in
the code. If it will compile, then you may want to compact and repair the
database. If that fails I recommend trying jetcomp.exe utility to see if
that will repair the problem.
 
Thanks for your help!

As a part of my debugging, I eliminated all code from the
DB (including macros and VBA modules and form modules).

I tried the compact/repair again after the code was
removed. It seems to get about 1/2 done, then just quits
and goes through startup. No error messages are given.

I find that even opening the table and browsing around,
then trying to close it, gives me the error "this action
will reset the current code in break mode", again with NO
code in the mdb!

Strange.
 
This is a generic error message (like 'out of memory')
that may occur at any time, for any reason. Your
experience is probably closer to
http://support.microsoft.com/default.aspx?scid=kb;en-us;234248
because you have corrupt data, not a corrupt project.

Import all the non-corrupt objects to the new database,
Import the structure of the corrupt table to the new database.
Use append and delete queries to move all the good data
from the bad table to the good table.

(david)
 
Back
Top