Discussion Locked

Access 97 Jet Database Error Message

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I got a new computer and our tech support people transferred the relevant files from my old computer to my new computer by saving them to our network and downloading them to my new hard drive.

In the process, something has occurred that will notallow me to open reports in our Access'97 database. First I receive a message that the default printer is busy and would I like to print on another network printer, which I answer OK. The I get an error message #3197 advising that the Microsoft Jet Database engine stopped the prcoess because of a conflict. I have reloaded Access'97 to no avail. Any ideas why this is happening and how I can

5 replies

by m.r.chambers

I went to Microsoft.com and search fro Error Number 3197 and the top hit contained this portion of an article:

http://support.microsoft.com/support/kb/articles/Q182/8/67.ASP

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.

I've never encountered this before, but I hope this helps you a bit. If not, try searching through the microsoft support stuff: if it's a problem that has occurred before, you can almost guarantee that MS has something about it on their site.

Hope that helps,
M.R.Chambers

by the professor

Reinstalling Access won't help because the problem is in the database. Most likely, the data did not properly migrate from workstation to server and onto the new one.

Try packing the database (I believe it is an option on the tools menu) or lookup packing the database on the help menu.

I've done this before to clear up database errors with success.

Good luck

This discussion is closed to new replies.