Booting users out of Access?

[db1]

I want to modify the design of some forms and do some other things
that I need to have the db opened exclusively in order to
accomplish.

Someone has Access open, but have locked their machine and left for
the day.

I assume it is this person because I right click on the .ldb file and
see there name in the security tab under users and groups.

Is there a way to boot people out and take over the DB exclusively
without damaging the data?

Thanks.

Also, does this forum have a search option?

[John Mishefske]

db1 wrote:

I want to modify the design of some forms and do some other things
that I need to have the db opened exclusively in order to
accomplish.

Someone has Access open, but have locked their machine and left for
the day.

I assume it is this person because I right click on the .ldb file and
see there name in the security tab under users and groups.

Is there a way to boot people out and take over the DB exclusively
without damaging the data?
Here's a popular solution:

http://www.datastrat.com/Download2.html - KickEmOff2K
Also, does this forum have a search option?

Yes, Google Groups.

--
'---------------
'John Mishefske
'---------------

[Keith]

"db1" <fa********@yahoo-dot-com.no-spam.invalid> wrote in message
news:lK********************@giganews.com...

I want to modify the design of some forms and do some other things
that I need to have the db opened exclusively in order to
accomplish.

Someone has Access open, but have locked their machine and left for
the day.

I assume it is this person because I right click on the .ldb file and
see there name in the security tab under users and groups.

Is there a way to boot people out and take over the DB exclusively
without damaging the data?

Yes there is but you have to design the feature into your app which usually
involves quite a bit of VBA code.

Also the idea of having one Access file for all objects in a multi-user
environment is a huge no-no because of the possibility of corruption. You
should have your app split into front and back ends and each user should
have their own copy of the front end. Search the help for "split database".

Regards,
Keith.
www.keithwilby.com

[aaron.kempf]

you're crazy.

screw MDB. use Access Data Projects. you can do things like this
easily. but you dont ever have to.

MDB is jsut too unreliable for realworld use.

[Bri]

aa*********@gmail.com wrote:

you're crazy.

screw MDB. use Access Data Projects. you can do things like this
easily. but you dont ever have to.

MDB is jsut too unreliable for realworld use.

Give it a rest. MDB works just fine with SQL. There are pluses and
minuses to both methods. Talking like you are here just makes you the
radical and makes you more likely to be ignored than listened to. If you
think that the specific problem can be solved with an ADP, then show us
how, don't just rant without backing up your statements.

--
Bri