Results 1 to 4 of 4
  1. #1
    2 Star Lounger
    Join Date
    May 2002
    Location
    Jerusalem, Israel
    Posts
    187
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I would like to prevent users from opening more than one instance of the same database.

    How do I do that?

    Thanks,

    JoeK

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts
    The only way I can think of to do that is to configure the user so they open the database exclusively - that's an option you can set. However that will also prevent other users from opening the same database if you are using a shared front-end. So you would need to deploy the front-end to each user's PC presuming that you have a multi-user situation.
    Wendell

  3. #3
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts
    Have a look at this .
    Regards
    John



  4. #4
    New Lounger
    Join Date
    May 2002
    Posts
    9
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I split my databases into front-end and back-end - the back-end is on a server, and the front-end is compiled into an .mde or .accde running on each user's PC.

    The back-end database has a Users table, which contains records for those who can use the database. Within this table is a flag called UserIn, which I set when a user first logs into the database, and unset when they log out of the database. This way, when a user tries to log in, I can check if they're already logged in and prevent duplicate use. I can also see who is using the database at any time.

    Of course, I have to unset this flag manually if their PC or the network fails, but this is rare.

Posting Permissions

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