|
Home > Archive > MS Access Multiuser > May 2005 > Throwing Users Out
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Throwing Users Out
|
|
| LarryP 2005-05-23, 8:25 pm |
| I have a split database (several, actually, but one will do as an example):
back end on a server, front end on each user's computer.
Back end gets refreshed each Monday between 6 and 8, and the front end has a
built-in warning message that " database is not available before 8:00 on
Mondays," then shuts down the database.
However, there's at least one smart-a** who knows enough Access to bypass
that message and signs onto the database before 8:00. That prevents me from
doing the refresh for the other 200-odd users.
Does anybody know a way that as the database owner I can go in and throw
anybody and everybody out of the database when I need sole access? At one
time I thought asking nicely would suffice, but obviously I'm going to have
to be a pr*** to keep reasonable control over the situation on Monday
mornings.
| |
| Rick B 2005-05-23, 8:25 pm |
| There are lots of ways. I have code in a hidden form that runs every 3 or 4
minutes. It looks at the value of a table (which nly has one field and one
record) and if that value is a "1" then nothing happens. If it is a "2"
then a pop-up warns the users that the database will close for maintenace in
5 minutes. If it is a "3" then it does the command "quit".
My startup macro checks the value of that table and does not let the
database open if it is a 2 or 3.
Do a search. There is a procduct I have seen mentioned that is called "kick
'em off". Go to google groups and search for...
microsoft.public.access kick off users
--
Rick B
"LarryP" <LarryP@discussions.microsoft.com> wrote in message
news:19E7FF6D-C0A3-438A-B4B3- 2760AAE443C8@microso
ft.com...
> I have a split database (several, actually, but one will do as an
example):
> back end on a server, front end on each user's computer.
>
> Back end gets refreshed each Monday between 6 and 8, and the front end has
a
> built-in warning message that " database is not available before 8:00 on
> Mondays," then shuts down the database.
>
> However, there's at least one smart-a** who knows enough Access to bypass
> that message and signs onto the database before 8:00. That prevents me
from
> doing the refresh for the other 200-odd users.
>
> Does anybody know a way that as the database owner I can go in and throw
> anybody and everybody out of the database when I need sole access? At one
> time I thought asking nicely would suffice, but obviously I'm going to
have
> to be a pr*** to keep reasonable control over the situation on Monday
> mornings.
| |
| LarryP 2005-05-23, 8:25 pm |
| Cool -- I'll try it.
"Rick B" wrote:
> There are lots of ways. I have code in a hidden form that runs every 3 or 4
> minutes. It looks at the value of a table (which nly has one field and one
> record) and if that value is a "1" then nothing happens. If it is a "2"
> then a pop-up warns the users that the database will close for maintenace in
> 5 minutes. If it is a "3" then it does the command "quit".
>
> My startup macro checks the value of that table and does not let the
> database open if it is a 2 or 3.
>
> Do a search. There is a procduct I have seen mentioned that is called "kick
> 'em off". Go to google groups and search for...
>
> microsoft.public.access kick off users
>
> --
> Rick B
>
>
>
> "LarryP" <LarryP@discussions.microsoft.com> wrote in message
> news:19E7FF6D-C0A3-438A-B4B3- 2760AAE443C8@microso
ft.com...
> example):
> a
> from
> have
>
>
>
|
|
|
|
|