Hi, all,

Here's what I want to do: I have 40 customers, each using the same version of my FM db. All currently operate independently of each other on their own machines. I would like to get FM Server, load a single master db on the FMS and have my customers all work from the one file. I am trying to figure out the best way to "partition" the single db so none of the customers can see each others' records, include them in reports, etc.

I created passwords/groups to limit records each customer can edit and delete. This works fine, except I can't figure out if there is a way to automatically hide or omit the records that say "access denied."

Any suggestions? Maybe I just need to look at this from a different perspective. Your expertise is most welcome.

It isn't the most elegant solution but to solve this problem I have users first start at an "Directory" page in which indicate their user name. They then select a button which opens the file they want to view. When the file opens a script is run which finds all of the records with their name in a field called "User". If the user wants find subsets of their records you can make this easier with scripts which perform finds using the "constrain found set" option.

What is this "constrain found set" option you speak of? Sounds like it might make my life a lot easier - but only if I know what it is and how it works!

Thanks, Mary Z : )

hi Mary,

the option to "constrain found set" is available in version 6.

From the FileMaker website:

"Constrain and Extend Found Set

Perform more sophisticated Finds by either constraining or extending an existing found set, without a series of complex steps."

cheers,

Wendy

Thanks for the info, Wendy. I'm using Developer 5.5, which explains why I didn't know about this feature.

I sure appreciate the collective wisdom and assistance of this group!!

Mary Z

Assuming the user is not active in a record to which he or she is denied access, a Go TO Related Records based on a constant relationship will return only those records to which the suer does have access.

Of course there are security issues with constant relationshios, so all these factors nmeed to be balanced.

Hi there, I am emailing you because I posted the same scenario in the relationship category. I was wondering if you've figured it out and willing to share what you learned. I am also working from one master db and would like to set it up so they can not see each other's records. I have passwords/groups but can't figure out how each one will only see their records.

Thanks for any assistance you can give me.

Examine the record level access privileges associated with Browse, edit, and delete records. You can thus configure the password so that the user sees only his/her own records. Determining record ownerhsip can be done at creation. The RLA calc matches up the record to the owner.

If you do a GTRR based on some criterion, it will return those records that belong to the user and no the <<access denied>> ones.