FATAL ERROR: Unhanded Access Violation Reading0xd6 Exception as ab096db4h

[Anonymous]

Anyone else getting this error? I get this while editing an item in the catalog database through the ACE interface. Other users are reporting this as well. It seems to happen while saving a entry. It seems to happen randomly and am just looking for some things to check as to why it could be happening. Our default catalog is on a network share.

[Icemanau]

Not 100% sure if this will be the cause or not, but it's possible that when the fault occurs, someone else is actually using the database so it's locked you out. This would explain the random nature of the problem and why several people are experiencing it.

To check requires every users co-operation.

First of all, get every user to just be working in ACADE without looking anything up or editing the catalogue. Edit and save and everything should go well.

Next have one user do a lookup and wait with the catalogue open while you do an edit and save.

Last test is for you to start an edit and then have a user do a lookup and wait with the catalogue open while you finish the edit and save.

Do you get the error popping up on any of those tests.

If so, repeat the test several times and see if the error persists. If the error pops up each and every time on the one test, you know what the problem is.

You didn't indicate what version of ACADE people are running at your location but 2018 has the option to use a SQL database for the catalogue rather than the MDB one. I'm just not sure that moving to a SQL database would be any help or not.

Regards Brad

[Anonymous]

Thank you for the response. I will try what you have suggested out. We are all using 2016 SP1. I have seen instances of users opening the MDB file in access and have asked everyone to not do this. But I will go through the steps suggested and see what happens.