No, it's not read only. I'm curious what caused it to not work this morning.Is the DB file read only?
I have backups but those were responding in the same way. I make backups periodically for this reason.If you do not have a recent backup, you might wish to make one now.
Seems possible, This DB is shared and used by 30-35 people but all are gone home by 5 pm. One of them may have left there's open.Perhaps you had an existing copy of the file left open & then opened a new instance of it. This could have caused some records / actions to become 'locked'
It is already split with a backend db. I've had it and have been using it for a few years and this has never happened until yesterday. The database started working again earlier today. However, I'm still curious what caused it to not operate as intended.Since you inherited this DB from your colleague, I have to ask if you know whether this is a split database with front end and separate back-end files. If you had a ragged closure that left a particular file (the .LDB or .LACCDB file) open, a temporary outage is not only possible but likely.
Thank you so much for your time and sharing your experience about my concern. Question, is there a way to know who would have my file locked in the event I need to find that out. As you mentioned, there are other possible causes for the disruption in functionality.The simplest explanation, but not likely to be the ONLY possible explanation, would be that a user had an abnormal exit that locked the lock file. When that same user logged back in, since they owned the file lock, if they had a normal exit, they cleared the lock - and let everyone else in. If so, there was one person who DIDN'T see the problem - because they were the cause.
But that's not the only possible explanation.
is there a way to know who would have my file locked in the event I need to find that out.