February 23, 200619 yr I have printed and read all the topics concerning permission to access specific records by multiple users, but I cannot find an answer to my question. I have several hundred records for multiple clients and I want to be able to allow a client to access his records only, through the user name or password that I will assign. Each and every record has a field called "customer". Any suggestions will be helpful. Nick
February 23, 200619 yr The way i do this is by specifying an extra field called Account. Account is an auto enter text that on creation gets the current account name. I then enforce forced finds when a user goes to a layout, searching for all records that were generated by their account. I also script finds using a constrain script that will constrain to the account after the user has specified their own criteria, note though that i do not use the filemaker bar on the left. Genx
February 23, 200619 yr The standard way of doing this is to use the Record Level Access settings in the privilege sets. Set Record Access to "custom", and per table, set the "view" (and edit,...) privilege to "limited". In the calc there you need to produce a result that is true or false depending on if they can see the records or not. How that calc looks like depends on how your solution is built but you'll need to compare some data from the record (who created it, most likely) to some other more global data (who is logged in).
February 23, 200619 yr I must say I never did enjoy specifying privelege sets and record access rights / viewing etc. Twas always a pain, though wim is right in this case, this is likely the best way for you to do it. I do mine the way i do because i sometimes have personal assistants logged in, who's account name wont match the person who originally created the record, so i almost forgot about filemaker privelege sets hehehe. ~Genx
February 24, 200619 yr Author Thank you all for your suggestions. I will look it over the weekend and I will probably come back for some more questions and guidance.
Create an account or sign in to comment