Error 3022 when navigating from one record to another record.

[bigdavidt]

Good evening.

Every few weeks there has been a problem caused by error 3022 on our main ORDERS form. When this happens it is because somebody is moving from one record to another record. We then boot everybody out of the front end database and use Compact and Repair to clean up the back end. The problem is then resolved for another couple of weeks.

I looked up the description and found (among other things) this:

The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again. This error occurs when saving changes to a report or generating a report.

I have a copy of the unrepaired back end and I have attached it to a copy of our front end for test purposes. I can get the error to recur, no problem. The problem is that it happens ONLY if I navigate from one record to another record. I have not made any changes to the data entries.

I have found several posts on Tek-Tips about this error, but so far nothing seems to fit what we have.

Does anybody have any thoughts on this?

Thank you in advance.

 

[lameid]

My gut reactions...

There is a flaky network device that is periodically causing the same error to occur in data. You may have some success if you ask people who made changes... logging might help if to a separate file.

There is a security product futzing with the file writes adding latency to the write to disk and lying to Access about it being complete. With it's multiuser fileserver nature this can lead to all kinds of issues. You'd probably experience others so I am guessing this is not it. I occasionally see writes not happen and I am thinking it is security software.

Your user base size, locking type and transactional velocity are simply at a point that Access is not coping with. Compact often, archive when you can, move to SQL server or have some serious thought about record contention and application design.

These are just my best shot in the dark guesses. I may be entirely wrong. Happy hunting!

 

[bigdavidt]

Thank you.