Tags: access, database, dbase, field, microsoft, mysql, oracle, password, protect, salary, sql, thedbase, theres

Can you password protect a field in Access?

On Database » Microsoft Access

4,288 words with 3 Comments; publish: Sun, 01 Jun 2008 12:51:00 GMT; (25062.50, « »)

We have an HR dbase with salary info. Is it possible to allow access to the

dbase without seeing the salary field? I don't think there's a way to

password protect a single field, is there?

All Comments

Leave a comment...

  • 3 Comments
    • You could have the form test to see if the user was a particular person or a

      member of a particular group, then set the field's visible property. It

      might be easier/safer/better to simply make two identical forms and remove

      the salary field from the one that will be used by most of your users, then

      set up the appropriate access so they can't open the other form.

      I assume that you have your database built in such a way that they can't

      simply open the query or the table and see the data there?

      Rick B

      "Tina" <Tina.ms-access.questionfor.info.discussions.microsoft.com> wrote in message

      news:26F83F31-E713-4C1C-9771-2104EF4412CD.ms-access.questionfor.info.microsoft.com...

      > We have an HR dbase with salary info. Is it possible to allow access to

      the

      > dbase without seeing the salary field? I don't think there's a way to

      > password protect a single field, is there?

      #1; Sun, 01 Jun 2008 12:53:00 GMT
    • Well, actually, we're beginners and haven't set the queries and tables to not

      be viewed. Can I password protect tables and queries? How would I set that

      up? Thanks.

      "Rick B" wrote:

      > You could have the form test to see if the user was a particular person or a

      > member of a particular group, then set the field's visible property. It

      > might be easier/safer/better to simply make two identical forms and remove

      > the salary field from the one that will be used by most of your users, then

      > set up the appropriate access so they can't open the other form.

      > I assume that you have your database built in such a way that they can't

      > simply open the query or the table and see the data there?

      > Rick B

      > "Tina" <Tina.ms-access.questionfor.info.discussions.microsoft.com> wrote in message

      > news:26F83F31-E713-4C1C-9771-2104EF4412CD.ms-access.questionfor.info.microsoft.com...

      > the

      >

      >

      #2; Sun, 01 Jun 2008 12:53:00 GMT
    • Have you put user-level security in place? You need to do that first. Read

      the Security FAQ document on the Microsoft website and make a backup before

      you begin. It will help you create a new workgroup file, build groups and

      users, tie the database to the workgroup, etc. If you are not careful and

      skip steps, then a user will be able to open your database on their

      computers without any userid and password, so once you think you are done

      test is on another computer.

      Once you have the security in place, you would set up userids and passwords

      for each user. You would have to take away all access from the tables and

      queries. You'd have to set the queries to Run with owner's permission and

      tie them to the forms and reports you wish to use. You'd only give them

      access to the forms and reports you'd want them to have.

      Note that adding a database password (one that any user can enter) is not

      going to allow you to protect individual items or specify different levels

      of security for different users. Also, you can buy a program for about $25

      on the Internet that will easily crack a database password. I think

      cracking user-level security is a bit more difficult, but I'm sure it can

      still be done.

      You have a great deal of reading and work to do before you can have a

      reasonably secure application. Note that Access is not "secure" and any

      savvy user will be able to get around these security measures. Access is

      not really a good tool for a payroll system.

      Good Luck,

      Rick B

      "Tina" <Tina.ms-access.questionfor.info.discussions.microsoft.com> wrote in message

      news:4E0D23CA-5C8A-4FF8-AB04-2021737B0B83.ms-access.questionfor.info.microsoft.com...

      > Well, actually, we're beginners and haven't set the queries and tables to

      not

      > be viewed. Can I password protect tables and queries? How would I set

      that[vbcol=seagreen]

      > up? Thanks.

      > "Rick B" wrote:

      or a[vbcol=seagreen]

      remove[vbcol=seagreen]

      then[vbcol=seagreen]

      to[vbcol=seagreen]

      #3; Sun, 01 Jun 2008 12:55:00 GMT