Requiring user to re-login periodically

[RussCRM]

I'm using the Access User-Level Security features with various users
set up.

I have a form/timer all set up to trigger an event after a period of
inactivity.

I'd like that event to log off a user and force them to log back in or
to require them to login periodically. The reason for this is that
multiple people use the database and I want to make sure the current
user is the logged in person.

Also, I'd like to configure a button for them to log off when they
walk away from the computer.

On top of that, I'm wondering if this can be done without kicking them
out of the database and having to reload it every time.

 

[Brendan Reynolds]

I'm using the Access User-Level Security features with various users
set up.

I have a form/timer all set up to trigger an event after a period of
inactivity.

I'd like that event to log off a user and force them to log back in or
to require them to login periodically. The reason for this is that
multiple people use the database and I want to make sure the current
user is the logged in person.

Also, I'd like to configure a button for them to log off when they
walk away from the computer.

On top of that, I'm wondering if this can be done without kicking them
out of the database and having to reload it every time.

To the best of my knowledge, no, there is no way to log out without closing
the database. If you want to do that, it's simply DoCmd.CloseDatabase.
You'll need to make very sure that your users really are not currently using
the application and have saved any pending updates, though. And at the end
of the day, will it really accomplish your goal? Doing this may decrease the
probability that the person using the app is not the person who logged in,
but it cannot completely prevent it.

 

[a a r o n . k e m p f]

sounds to me like you're be much better off using Integrated Windows
Security with SQL Server and Access Data Projects

File, New, Project (existing data) in Access 2003

 

[Rustle]

Thanks for the advice! I've never gone to the level of an Access Data
Project, but we'll give it a try!

I don't suppose there's a way to close the database and then reopen it
via code is there?

 

[BruceM]

I urge you to check out other postings by Aaron. His invariable
"suggestion" to use ADP and SQL Server has been "discussed" at length, and
seems to be recommended mostly by Aaron. He does not have a history of
providing solid, detailed advice. Also, ADP is supported for backward
compatibility, as I understand it, so it may not be the best choice for a
new project.

 

[Rustle]

Thanks! I've been learning about database design on the fly for about
a year now and still feel like I've barely scratched the surface! So
many "simple" ideas to you pros are an enigma to us newbies, so know
that we appreciate the help immensely!

 

[aaron.kempf]

yes, there is

in ADP, you can look at NorthwindCS.adp in order to see how to drop
and recreate the database connection

 

[RussCRM]

I tried looking at this but it requires SQL Server 2000 Desktop
Engine, which I can't figure out how to install.