privacy settings RRS feed

  • Question

  • I  have an access data base and would like to share it but keep some aspects of the data private. Is this possible?


    Friday, March 16, 2018 12:17 PM

All replies

  • Share it with? Coworkers?

    There are some things you can do, but if it is really important/sensitive info then I'd recommend turning to SQL Server (Express is free) because then you could create views to restrict access to info and only share those views with others.

    If you want to stay in Access, then you could create separate forms/report for other to use in which you've removed the fields that you don't want them to have access to.

    Daniel Pineault, 2010-2017 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Friday, March 16, 2018 12:43 PM
    1. Do what Daniel suggests and create a seperate database file for those users who should not have access to whatever information is contained on your input forms. Do NOT delete any of the controls on the forms. Simply set the 'Visible' property for those controls on the forms to 'No' that you do not wish to be displayed.
    2. Make sure the database file is split into Front-end and Back-end files with the Back-end residing on a shared network drive. After that, distribute the Front-end file to each user so that each user has their own copy on their computer. The users that input data get the Front-end file that shows all controls on all forms. The users that have restiricted access to data get the file with form control 'Visible' properties set to 'No'.
    3. Test both Front-end files to make sure everything works properly and change any macros or VBA code where needed.
    Friday, March 16, 2018 3:11 PM
  • I think the key question here is how you want to identify your users. Windows authenticated user? Database user? These are the two SQL Server security options that are available. You may want to consider Daniel's suggestion since they are built in.

    For an Access database I would encrypt the sensitive data and then decrypt it based upon whether the current user ID has privileges. Beyond that I think we would need to know how private this data needs to be. As it stands, the built in Microsoft Access security features are not all that secure and determined and somewhat knowledgeable users can work around it.

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Friday, March 16, 2018 4:02 PM
  • Hi colleencleasby,

    Is your issue is solved now?

    I find that you did not done any follow up after creating this thread.

    If your issue is fixed by you then I suggest you to post your solution and mark it as an answer.

    If your issue is still exist then try to refer the suggestions given by the community members.

    If you think that the suggestions given by the community member can solve your issue then mark the helpful suggestion as an answer.

    It will help us to close this thread and it also can be helpful to other community members who will meet with same kind of issues in future.

    If you have any further questions then you can let us know about it, We will try to provide you further suggestions to solve it.

    I suggest you to update the status of this thread and take appropriate actions to close it.

    Thanks for your understanding.



    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, March 21, 2018 9:53 AM