Results 1 to 5 of 5
  1. #1
    2 Star Lounger
    Join Date
    Oct 2001
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    136
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Exclusive Access to linked databases (Access 2000)

    Hello Access Gurus,

    I am having a problem with multi-sharing a linked database on a network. There is a main database that is used to add/edit records by a select few users (called the File Tracking (Admin) database) and I have linked another database to the Admin one that only enables a user to read the records and not change them (File Tracking Read-Only version). Both databases have the same Advanced properties of Shared, No Locks and Open Database using Record locking in Access. Both databases are located in different folders on the same network drive which used to have access priveleges associated with them. The users that had access to the Admin version had Full Control to modify, read&execute, List Folder Contents, Read and Write etc. whereas the Read-only database was restricted to Modify, Read&Exceute, Read, Write and List Folder Contents.

    Since we thought there were problems with the access priveleges, we removed all priveleges associated with each file and we are still getting the same error message. When the user opens the Read-Only version of the database which links to the Admin db we get the error message that I have included with this post.

    Has anything changed in Access 2000 concerning the sharing of databases? This method didn't pose problems in Access 97.

    Looking forward to a response.

    Cheers,

    Jocelyn

    The
    Attached Images Attached Images

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

    Re: Exclusive Access to linked databases (Access 2000)

    In itself, it is perfectly possible to use a setup like this.

    Make sure that the users who need to use the "read-only" version have full permissions in both the folder where the Admin version resides and in the folder where the Read-only version resides. You'll have to restrict what the users can do within the Access databases, not at the file or folder level.

    Also make sure that you don't try to modify the design of any database object while it is in use. This requires the user to open the database exclusively in Access 2000 and up; in Access 97 and before that wasn't necessary.

  3. #3
    2 Star Lounger
    Join Date
    Oct 2001
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    136
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Exclusive Access to linked databases (Access 2000)

    Thanks Hans,

    I was trying to avoid using the Security within Access but it looks like it is inevitable. So you are saying that linked databases can not use network security for restrictions any more? And the linked databases must have full network access privileges at the file and folder level and security set within each database.

    Cheers,

    Jocelyn

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

    Re: Exclusive Access to linked databases (Access 2000)

    As far as I know, Access has always required that users have read/write/create/delete permissions on the folder containing the database.

    In the first place, Access keeps track of who opens a database in a .ldb file. This file *must* reside in the same folder; it is created when the first user opens the database, updated each time opens or closes the database and deleted when the last user closes it.

    In the second place, Access creates internal temporary objects and writes these to the database file even if you only look at the data without editing them.

    If your only goal is to prevent some users from accidentally changing data, but you're not concerned about intentionally trying to break into the database, you can create a "read-only" front-end by making all forms read-only: set the Recordset Type property of all forms to Snapshot. Set Startup options to hide the database window, standard toolbars, etc.

    But if you want "real" protection, user-level security is the way to go. It is not as difficult as it seems. Take a look at the tutorial on <!profile=WendellB>WendellB<!/profile>'s website; it provides a short introduction to security and lots of useful links.

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

    Re: Exclusive Access to linked databases (Access 2000)

    Access has NEVER been amenable to network level security measures. I've fought IT departments over this for years and through 4 versions of Access because network people always assume you can control it at the file/folder level. One big difference starting in 2000 is that exclusive means just that. If someone has an exclusive lock on a database, you can't open a "read-only" copy of it. You can't open it at all under those conditions because an exclusive lock is required to make design changes and to compact in Access 2000 and later.
    Charlotte

Posting Permissions

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