Record-Locking Error

[Matthew DeAngelis]

I am experiencing a problem with a particular record in Access that is
extremely persistent. I hope someone in here can help me.

The database is split into a front and back end, although everyone on
the system uses the same frontend (not ideal, I know, but I did not
design it). There is a particular record that I entered today that
contains a lot of information identical to a previous record. As I was
copying and pasting these few fields over, I tabbed to the next field
and was greeted by this error: "The Microsoft Jet database engine
stopped the process because you and another user are attempting to
change the same data at the same time. (Error 3197)" However, there is
no one else logged into the database, much less editing that record
that, as I mentioned, I was in the process of entering for the first
time.
I viewed the Access Help entry, and it tells me: "To overwrite the
other user's changes with your own, execute the Update method again."
However, there is no option on the alert window of the error (I have OK
and Help) to do that, and the error recurs no matter how many times I
try to leave the field. All I can do is close the form, which then
erases my changes.
I changed error locks to "No Locks" and unchecked the box to "Open
database using record-level locking" and restarted the database, but
that did not help (I have since restored the original settings). I
compacted and repaired the database twice, which also had no effect. I
tried to change the table manually in the backend, but I received the
same error.
When I leave the database, there are no .ldb files in the folder, and
the server indicates that no one is using the database once I have left
it, and that I am the only user when I reopen it. Does anyone know
what could be causing the conflict and how I can fix it? It would be
nice if there was a button allowing me to force changes, but leave it
to Microsoft to make a "failsafe" that is more powerful than the user.

Thanks.

 

[Raghu Prakash]

Hi Matthew,

Error message:
The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time.

Cause/Problem:
This error typically occurs when a long value column (an OLE or MEMO
data-type) has bad data stored in it. Long value columns are typically
stored in a separate page from the page that the row is stored in. If a
long value column is present in the table schema, the Jet database engine
will attempt to read the long value page when reading the row of data. In
order to read the long value page, there is a pointer in the row of data.
This error is generated when the Jet database engine cannot properly read
the long value page from the pointer present in the data row. When viewing
a row that exhibits this behavior in Microsoft Access data-windows, the
user will typically see the number sign (#) for the entire row.

RESOLUTION
The Microsoft Jet database engine version 3.51 has an enhanced compact
process designed to remedy the problems (if possible) described in the
"More Information" section. The improved compact process now assumes all
the functionality of the repair process, and therefore it is no longer
recommended that you use the Jet database engine repair process.

NOTE: The Microsoft Jet database engine version 3.51 update is designed for
Microsoft Access 97. You can run the compact utility on a database created
in an earlier version of Microsoft Access; however, running the compact
utility, "JETCOMP.exe", requires that Microsoft Access 97 be installed on
your computer.

For more information about downloading the Jet database engine 3.51, please
see the following article in the Microsoft Knowledge Base:
172733 ACC97: Updated Version of Microsoft Jet 3.5 Available for Download

REFERENCES
For more information about the enhanced compact process of the Jet database
engine 3.51, please see the following file, which is included as part of
the Jet35sp3.exe (Jet 3.51 update) download:
Jet35SP3.doc

For more information about Microsoft Access 97 error codes, search the Help
Index for "reserved error codes," or ask the Microsoft Access 97 Office
Assistant.

For more information about repairing Jet databases, please see the
following article in the Microsoft Knowledge Base:
109953 ACC: How to Repair a Damaged Database

Please let me know has this helped You...
Thank you...
Raghu...
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Matthew DeAngelis]

Hi Matthew,

Error message:
The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time.

Cause/Problem:
This error typically occurs when a long value column (an OLE or MEMO
data-type) has bad data stored in it. Long value columns are
typically stored in a separate page from the page that the row is
stored in. If a long value column is present in the table schema, the
Jet database engine will attempt to read the long value page when
reading the row of data. In order to read the long value page, there
is a pointer in the row of data. This error is generated when the
Jet database engine cannot properly read the long value page from the
pointer present in the data row. When viewing a row that exhibits
this behavior in Microsoft Access data-windows, the user will
typically see the number sign (#) for the entire row.

RESOLUTION
The Microsoft Jet database engine version 3.51 has an enhanced
compact process designed to remedy the problems (if possible)
described in the "More Information" section. The improved compact
process now assumes all the functionality of the repair process, and
therefore it is no longer recommended that you use the Jet database
engine repair process.

NOTE: The Microsoft Jet database engine version 3.51 update is
designed for Microsoft Access 97. You can run the compact utility on
a database created in an earlier version of Microsoft Access;
however, running the compact utility, "JETCOMP.exe", requires that
Microsoft Access 97 be installed on your computer.

For more information about downloading the Jet database engine 3.51,
please see the following article in the Microsoft Knowledge Base:
172733 ACC97: Updated Version of Microsoft Jet 3.5 Available for
Download

REFERENCES
For more information about the enhanced compact process of the Jet
database engine 3.51, please see the following file, which is
included as part of the Jet35sp3.exe (Jet 3.51 update) download:
Jet35SP3.doc

For more information about Microsoft Access 97 error codes, search
the Help Index for "reserved error codes," or ask the Microsoft
Access 97 Office Assistant.

For more information about repairing Jet databases, please see the
following article in the Microsoft Knowledge Base:
109953 ACC: How to Repair a Damaged Database

Please let me know has this helped You...
Thank you...
Raghu...
This posting is provided "AS IS" with no warranties, and confers no
rights.

Despite the fact that I am using Access 2000 and do not have any long
value fields in that table, it worked like a charm! Thanks! I will
keep that utility around for later usage.