Hi, all -
We are using Access 2013 for a split shared database.
I know this is a common issue but the lccdb file for our shared backend db does not close, even when all users seem to be out of the FE database. I've done research but haven't found a solution. All our users have complete rights to the folder the houses the BE file.
Our users are required by our customer who manages our IT and the server to not shut down their computers at the end of the day - the sleep mode on their computer is enough for system management by, again, external customer IT.
I have the FE programmed to close after 10 minutes of inactivity. Does this shut down access completely, including the link to the backend?
I'm trying to figure out why so many are indicated as connected to the BE file when they shouldn't be.
One solution may be to have each user restart their computer at the end of the day. This would severe, I would hope, any connections to the BE file and hopefully close the lccdb file.
Would creating a dummy form in the BE that is bound to a primary table be programmed to close the BE DB after 10 minutes be a solution?
Any thoughts or suggestions?
Thanks.
We are using Access 2013 for a split shared database.
I know this is a common issue but the lccdb file for our shared backend db does not close, even when all users seem to be out of the FE database. I've done research but haven't found a solution. All our users have complete rights to the folder the houses the BE file.
Our users are required by our customer who manages our IT and the server to not shut down their computers at the end of the day - the sleep mode on their computer is enough for system management by, again, external customer IT.
I have the FE programmed to close after 10 minutes of inactivity. Does this shut down access completely, including the link to the backend?
I'm trying to figure out why so many are indicated as connected to the BE file when they shouldn't be.
One solution may be to have each user restart their computer at the end of the day. This would severe, I would hope, any connections to the BE file and hopefully close the lccdb file.
Would creating a dummy form in the BE that is bound to a primary table be programmed to close the BE DB after 10 minutes be a solution?
Any thoughts or suggestions?
Thanks.