Error messages with this number and text have been reported as long as 14 years ago - maybe longer. The general consensus is that it's corruption and requires you to import everything into a new BE. That may be the best option in light of the information you seem to have. Out of curiosity, I'd try copying the BE to a local hard drive and linking the tables to it and see what happens. Of course, any edits to this data would put it out of sync with the working data set, so it's just an experiment. If the BE is corrupt, copying it should have no effect, so the test should be valid. If you cannot replicate the failure after several attempts, it may be a network issue. However, you need to know what the user is doing at the time the error is generated. In fact, you need to know the process they are following. Often, knowing what is going on at the moment is insufficient as it can be just as important as to how they got to where they were just prior to the failure.
Last edited by Micron; 06-26-2017 at 10:02 PM.
Reason: added info
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.