Even your description,
Originally Posted by
Gryphoune
...I've never seen this happen before and somewhat perplexed as to the cause...
Points to this being non-split as the cause of your problem! The really insidious thing is that this kind of setup can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!
The record, by the way, was a Non-Split db that had been working, without problems, for 12 years! It then started exhibiting the problem detailed here and continued to do so until the app was split.
If your Database isn't really important, which is to say if data-loss isn't important, and the app being down won't cost you production time loss, then by all means leave it non-split.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007