Results 1 to 11 of 11
  1. #1
    2 Star Lounger
    Join Date
    Nov 2001
    Location
    London, UK, England
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Force Disconnect (Access 2000)

    Is there any way to force all connections to a back-end database to be dropped?

    We have a network database back-end and an MDE distributed to multiple clients. The database BE has become corrupted and we need all users out before we can repair. Unforutunately, a few had gone on lunch, locking their PCs and still logged in to the DB! So, we have to sit and wait...

    I could write a bit of code on a timer that constantly checked for a value in a table, then closed the DB if the value = LOG_OFF?

    Just interested to see if anyone else has this problem & what solutions there are if any...? Upgrading to SQL Server is high on my list...!!

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Force Disconnect (Access 2000)


  3. #3
    2 Star Lounger
    Join Date
    Nov 2001
    Location
    London, UK, England
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Force Disconnect (Access 2000)

    Thanks Hans, that's a better version of what I was going to write...!!

    You would've thought an admin tool for doing this would've been shipped with Access...?!

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Force Disconnect (Access 2000)

    Access isn't designed for that. If you want to do that sort of thing, you have to build it yourself and build the companion logic into the Access application. This is even more true of Access 2000 and 2002 than prior versions. Database servers like SQL Server have that kind of admin tools built into them, but Access is a file server application, and is designed not to require a database administrator.
    Charlotte

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Force Disconnect (Access 2000)

    By the way, you *can* externally keep anyone new from logging into a 2000/2002 database although it won't force those currently logged in to get out. The sample code found here and there to do this is both misleading and incomplete. I just had to work out that functionality for one of our products, so I know whereof I speak! <img src=/S/hairout.gif border=0 alt=hairout width=31 height=23> It does require ADO, though. There just isn't any way to do it with DAO.
    Charlotte

  6. #6
    2 Star Lounger
    Join Date
    Nov 2001
    Location
    London, UK, England
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Force Disconnect (Access 2000)

    Thanks Charlotte, I think I'm going to try and write some sort of COM DLL to do this....if I have any joy I'll make the source available...!

    It's even more of a nightmare in our company at the moment - we've just moved onto a thin-client network and hardware ID's logged in the locking files now just display the ID of the server. We're forcing everyone in through a workgroup to log their user ID as well, but in some cases users are linking tables to BE databases from unsecured DB's! This means we can't identify which users are locking files & have no way to remotely disconnect them... <img src=/S/brickwall.gif border=0 alt=brickwall width=25 height=15>

  7. #7
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Force Disconnect (Access 2000)

    Access security on the back ends as well as front ends should put a stop to that.
    Charlotte

  8. #8
    3 Star Lounger
    Join Date
    Nov 2001
    Location
    Sydney, New South Wales, Australia
    Posts
    216
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Force Disconnect (Access 2000)

    I was reading through this post and the last comment from Charlotte intrigued me. How do you add security to the back-end as the front-end? Actually, that's a little simplistic - what I really want to know, is it possible to secure both the back and front-end files using the identical user names and passwords? That is, where there are multiple user names each with their own passwords for the front-end, could these also work concurrently with the back-end. I guess there would only be one .mdw file. If so, how is this setup?

  9. #9
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Force Disconnect (Access 2000)

    Permissions live in the database itself. Only the passwords and logins live in the mdw file. So if you apply the same user groups and use accounts to the back end, then you can use the same workgroup file to control access to the back end. That's they way our applications are secured and it works quite well. Because the Admin user has no permissions, no one can open the backend unless they have joined the appropriate workgroup.
    Charlotte

  10. #10
    3 Star Lounger
    Join Date
    Nov 2001
    Location
    Sydney, New South Wales, Australia
    Posts
    216
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Force Disconnect (Access 2000)

    Yes, that all makes sense. Is there an article you can point me to or a set of instructions you can give me to make this all happen? I have been using the 'User-Level Security Wizard' so far. Is that all I need to secure both ends - assuming I'd need to use the wizard once for the front-end and again for the back-end?
    Thanks

  11. #11
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Force Disconnect (Access 2000)

    Using the Wizard on the front end and on the back end should work.

    Microsoft has a comprehensive overview of user-level security in ACC2000: Microsoft Access Security FAQ Available in Download Center. For more links, see WendellB's The Secrets of Security.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •