Results 1 to 6 of 6
  1. #1
    Join Date
    Aug 2005
    Posts
    196

    Unanswered: MDW Read Only Read Only User

    Hi,

    I have an exisiting Database that allows the user to set up New users with full read/write access. Is there a way you can allow them to set up a user and assign that user to have a read only profile, by checking a box during the creation, giving full read access but not allowing them to change any data whatsoever? Cheers.

  2. #2
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    assign them to an appropriate work group......
    I'd rather be riding on the Tiger 800 or the Norton

  3. #3
    Join Date
    Aug 2005
    Posts
    196
    The thing is, I'm using a book as a reference and there is a list of Permission Contraints (e.g. dbSecInsertData, dbSecDeleteData etc), however, there is no such contraint to set read only???

  4. #4
    Join Date
    Jan 2007
    Location
    UK
    Posts
    11,444
    Provided Answers: 12
    Are you using the built-in access security - if so - read only properties can be set for a group in there.
    George
    Home | Blog

  5. #5
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,469
    Provided Answers: 10
    please back up you work

    last time i play in there i lost a database
    about ten years ago
    hope this help

    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
    DONT WORRY ABOUT THOSE WHO TALK BEHIND YOUR BACK
    THEY'RE BEHIND YOU FOR A REASON

  6. #6
    Join Date
    Nov 2004
    Location
    Harrogate, N.Yorks, UK
    Posts
    83
    You may need to run the security wizard to add a 'Read-only users' workgroup prior to being able to assign the user to that workgroup. As myle says, always get to grips with the security on a file you can afford to lose and avoid the system.mdw if you can- I've come unstuck there in the past. It's a good idea for each database to have it's own .mdw file rather than using the system.mdw

Posting Permissions

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