Using passwords to stop people looking at records

[ACTSA@ACTSA]

I designed a database to keep people's personnel records. There are 8 members of staff so 8 records within the database. But I want people to only be able to access their own record. I've had a look through the past messages and can't find anything that a) quite matches what I'm doing and : I understand the solution to!

I've played with passwords before, but I can't seem to figure out how to do what I want in this case. Can anyone help?

Thanks

Nicole

[LiveOak]

The key here is Groups. If you make each password it's own group, you can use the Browse, Edit, Delete control in the Password part of Access Privileges to do this. If you check Status(CurrentGroups) as a condition of Browse access you can prevent a user from seeing a particular record.

Realistically, this is the protection, but you don't want to dump a user on a blank screen. You would use a check of groups to not allow them the navigate to other people's records.

-bd

[ACTSA@ACTSA]

Hello

Thanks for this info - not sure I completely understand! My thinking was that I'd give everyone a different password that they would log on with. Is that what you meant? I don't get what you mean by "give every password a different group". I have to admit I find the whole password thing very difficult to get to grips with. It's the one thing that doesn't seem logical to me - I shall have to play with it more.

I'm guessing you get people to log on with different passwords and then when they want to go to a specific record a script checks that they're allowed to using the Check current status thing. Have I understood right?

Thanks

Nicole

[LiveOak]

You really will need to read and re-read the password/groups/access privileges section of the FM manual.

The basic thing is that you cannot test what password a person logged on with. You can, however, assign a password to a group. If you have only one password per group, testing Status(CurrentGroups) will tell you which person logged on.

Next, you can control access to a record with a calculation. By identifying each record with a group (person), you can only allow them access if the group assigned to the record (stored in a field not displayed) matches Status(CurrentGroup).

Sorry if this doesn't make sense, things are only as simple as they are.

-bd

[Pupiweb]

If you foresee that the user number will change quickly take into consideration to create a custom login scheme matched with a Users.fp5 file

(to see an example get a tip file named "The Gateway" at http://www.fmfiles.com)