access 2007

I have a database that 3 users use.  At 7 p.m I want to log the users out of the database automatically if they do no shut down there machines on there own.  Is that possible.  The users are not required to setup a userid an password to use the database.
centralmikeAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

peter57rCommented:
Use a hidden form that runs a timer event every hour say.

In the timer event procedure check the time and when you get to after 6 oclock then change the timer inetrval to every 10 minutes and once you get to 7oclock issue a message box that the app will close automatically in 10 minutes.  
Then on the next timer event close the app.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jeffrey CoachmanMIS LiasonCommented:
Pete posted the most popular solution.

When you get this going, you might want to consider what to do if the user is in the middle of something when the DB shuts down.

Ex.:
They were in the middle of editing a record when they ran to the bathroom and did not see the alert.  What of the uncommitted edits?

What if they were running a long procedure, and the DB shuts down (Do you have "Roll-Back" Code in place)?

Your next Question here might be to find a way to give the user a "Need More Time? option...
;-)

Jeff
Jeffrey CoachmanMIS LiasonCommented:
Oh, and please do not consider my post for any points, as Pete's post would seem to be a valid solution.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

todd_beedyCommented:
Peter's post is def the correct one to use...

one word of caution... if you force people to log off and they are in the middle of something, you do risk corrupting your database. Be careful.

Here is an example of what he is talking about.

http://www.databasejournal.com/features/msaccess/article.php/3548586/Auto-Logout-Users-for-DB-Maintenance.htm
Jeffrey CoachmanMIS LiasonCommented:
...todd_beedy
<one word of caution... if you force people to log off and they are in the middle of something, you do risk corrupting your database. Be careful.>
...That is what I mentioned in my post: 37758539

...but the link is a bonus.


In addition to the home grown solutions, FMS inc provides a full featured app as well.

This might be a good fit for Distributed or higher end Production databases.
http://www.fmsinc.com/microsoftaccess/monitor.asp

JeffCoachman
centralmikeAuthor Commented:
The procedure worked as expected from your response
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.