Back End Read-Only Issue

[isladogs]

1. Setting up an inactivity shutdown is a good idea for other reasons but i won't help with this specific issue. When the laptop lid is closed Access (and all other open apps) will remain in the state they were left in and should restore automatically when the laptop is next opened.
Is that what you want to happen?

2. SQL Server will provide a more stable and secure BE than Access, particularly if you have many simultaneous users

 

[thomas.dickens]

Is that what you want to happen?

I need to protect the database from poor user behaviour - specifically, users the close their laptops without safely closing the database. I know that training is a strong defence but some of the users have low IT literacy and seem to continually do this despite training. The additional problem is that some of these users are regularly in and out of the office (clinical staff that attend clinics) and therefore sometimes they close the laptop, locking up the back end, and there is no way of accessing their laptop until they return the next day.

so yes, I do want the access to restore when the laptop reopens, but really I need a way to be able to force close the database after a laptop has been closed. OR I need a system that is robust enough to not get locked up in this scenario - thus the question re sql server.

 

[isladogs]

That's what I assumed. I would suggest both moving the BE to SQL server and setting up a system to automatically close the FE after a specified period of inactivity e.g. 20 minutes.
However, as far as I am aware, neither of those will help manage them just closing the laptop lid as the system will go into 'hibernation' so no code will run whilst the lid is closed. The laptop will indeed remain connected to the BE and may prevent routine maintenance work being carried out.

 

[thomas.dickens]

That's what I assumed. I would suggest both moving the BE to SQL server and setting up a system to automatically close the FE after a specified period of inactivity e.g. 20 minutes.
However, as far as I am aware, neither of those will help manage them just closing the laptop lid as the system will go into 'hibernation' so no code will run whilst the lid is closed. The laptop will indeed remain connected to the BE and may prevent routine maintenance work being carried out.

Thing is it is worse than preventing routine maintenance work - it puts the BE into read only mode and no users can edit any data whatsoever. One user being careless can halt the entire team!

Thanks for the advice - will look into migrating to s

 

[isladogs]

I'm still unclear why doing that would put the BE into read only mode
Whilst still a good idea for stability and other reasons, I don't believe SQL Server will solve that issue

 

[thomas.dickens]

Your guess is as good (or better) than mine...

This didn't seem to be an issue for the first ~3 months of usage, and I am sure that the users' habits were just as bad back then as they are now!

 

[Gasman]

Whilst my BEs are on the same laptop as my FEs, I have had to switch off my laptop several times with the power key?
Never once has a BE DB become read only?