Results 1 to 10 of 10
  1. #1
    Gold Lounger
    Join Date
    Feb 2004
    Location
    Cape Town, RSA
    Posts
    3,444
    Thanks
    0
    Thanked 1 Time in 1 Post

    Make linked tables read-only! (Access 2000 >)

    Can a linked table be make read-only without using user-level security?
    Tx
    Regards,
    Rudi

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

    Re: Make linked tables read-only! (Access 2000 >)

    Strictly speaking, no. And as long as you don't use user-level security, users can just get at the backend data directly... <img src=/S/evilgrin.gif border=0 alt=evilgrin width=15 height=15>

    You should never let users work with data directly in a table or query, only through forms. You CAN make the data in a form read-only, by setting the Recordset Type property to Snapshot. Combined with the usual measures of hiding the database window etc. this will prevent the users from accidentally editing data.

  3. #3
    Gold Lounger
    Join Date
    Feb 2004
    Location
    Cape Town, RSA
    Posts
    3,444
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Make linked tables read-only! (Access 2000 >)

    Thank-you. Appreciate the advice too!
    Cheers
    Regards,
    Rudi

  4. #4
    3 Star Lounger
    Join Date
    Jun 2001
    Location
    Salem, Oregon, USA
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Make linked tables read-only! (Access 2000 >)

    Unless the data end is on a network with network privs that allow read-only for some and write for others, right?

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

    Re: Make linked tables read-only! (Access 2000 >)

    Access requires that users have full permissions (read/write/create/delete) on the folder(s) containing the frontend and backend databases.

  6. #6
    3 Star Lounger
    Join Date
    Jun 2001
    Location
    Salem, Oregon, USA
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Make linked tables read-only! (Access 2000 >)

    Right, I know, so this is how I do it: I give everybody "modify" privs on the whole folder, so they can create, modify, and delete the lock files. I leave it that way except for locking down the Master & Backup Folder, in other words, the install folder is left pretty open, but that's okay. Then, I further refine the network privileges to make the FrontEnd database be read/write/execute for everyone (in other words, remove the modify priv), and the BackEnd database gets read/execute for some and read/write/execute for others. (As an aside, I used to install the front-ends on their c: drives, but, I found that every change required a copy-down... so I opted to have both run on the network.)
    thx
    Pat

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

    Re: Make linked tables read-only! (Access 2000 >)

    Looks OK. I never do it that way because in the organization where I work, it's a hassle to get the IT department to assign non-default permissions to network folders (I can't do that myself), so I don't bother.

  8. #8
    3 Star Lounger
    Join Date
    Jun 2001
    Location
    Salem, Oregon, USA
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Make linked tables read-only! (Access 2000 >)

    It is a hassle, but I do it. Various times a person or two has said, "that's the network guys' responsibility," but that's even more of a hassle <gg>.
    thx
    Pat

  9. #9
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Make linked tables read-only! (Access 2000 >)

    You pay a significant performance penalty when the front-end is located on a network drive, especially if users are sharing the same copy and you have complex forms or reports. You also have the issue of the front-end going corrupt because of network problems, PC crashes and the like. We use a home-grown product to deploy to the user's workstation - we've used it successfully with applications where we have 200 workstations accessing a SQL Server back-end. If a front-end goes corrupt, only that user is affected, and they can simply download a new one. http://www.fmsinc.com has a commercial product called Startup that is pretty sophisticated too.
    Wendell

  10. #10
    3 Star Lounger
    Join Date
    Jun 2001
    Location
    Salem, Oregon, USA
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Make linked tables read-only! (Access 2000 >)

    Thanks, Wendell. I know I should -- so far, people haven't complained -- that I know of.
    thx
    Pat

Posting Permissions

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