Hi Rick. Thank you for the great content. I have the exact same function built in to the database I manage, however I just have a simple yes/no field in a settings table. When the main form's timer is triggered, it looks whether the yes-no field is True or False. If it is True, it opens op another form that counts down from 60 seconds, then closes the database. In my admin menu, I can toggle this yes/no field on and off, so that I can easily kick out all users if I need to do maintenance. I call this function the "FE Lock" (front-end lock). Over the past week, I have made this system much more advanced and automated. If you need inspiration for your future videos, here is what I have built lately; I have made a "server application", which is just another simple Access file that is permanently open on our server machine - the same one that hosts the file server where the backend database is located. This "server application" has a simple form with a timer, and is programmed to perform certain tasks at different times. At midnight, it automatically engages the "FE Lock" so that nobody can login. It then creates a backup of the backend, performs a compact & repair on the backend, and then disables the FE Lock again. Also, every 60 seconds, it moves data from a SharePoint list into the Access backend database. This is because our sales reps collect data in the field through a phone app that I built in PowerApps, however the rest of our enterprise solution is built completely in Access, and we prefer to keep everything there.
Hi Rick. Thank you for the great content. I have the exact same function built in to the database I manage, however I just have a simple yes/no field in a settings table. When the main form's timer is triggered, it looks whether the yes-no field is True or False. If it is True, it opens op another form that counts down from 60 seconds, then closes the database. In my admin menu, I can toggle this yes/no field on and off, so that I can easily kick out all users if I need to do maintenance. I call this function the "FE Lock" (front-end lock).
Over the past week, I have made this system much more advanced and automated. If you need inspiration for your future videos, here is what I have built lately; I have made a "server application", which is just another simple Access file that is permanently open on our server machine - the same one that hosts the file server where the backend database is located. This "server application" has a simple form with a timer, and is programmed to perform certain tasks at different times. At midnight, it automatically engages the "FE Lock" so that nobody can login. It then creates a backup of the backend, performs a compact & repair on the backend, and then disables the FE Lock again. Also, every 60 seconds, it moves data from a SharePoint list into the Access backend database. This is because our sales reps collect data in the field through a phone app that I built in PowerApps, however the rest of our enterprise solution is built completely in Access, and we prefer to keep everything there.
Sounds awesome thanks for sharing
Thanks for the informative video! Richard, why didn't you use "2063-04-05" for your shutdown date?!
I know! What was I thinking!?
Thanks
Welcome
I have the database shut down after 20 minutes of non use
Yep that's easy to program as well
Very useful video.
Thanks a lot