Hi all,

Currently at work here we have a very messy database that has NO security, the previous database guy left the database in a shambles and we have over 150 databases we need to implement security on. At the moment, if anyone wants to enter some data, everyone in the company shares the same login, they can edit, delete and create new data, its a nightmare.

So we are implementing individual logins based on Active directory, however for the time being we want to create 3 log ins. Developer access(can do everything), Data Entry(without the ability to delete records) and Data Entry(with the abitlity to delete records).

Now we were testing this out yesterday and it appears we would then need to create the permission access to each database individually, is there a way we can create the permissions we want on one database, and propagate the permissions to all databases on that server?

We have 2 Filemaker servers, one on a windows 2003 machine and on the other on a mac Xserv running OS X. Running filemaker server 8 and the clients use 8.5. We are just testing this on the windows 2003 machine for now to make sure it is all running correctly before we try it on the mac server as well.

Permissions, ie., Privilege Sets, are table-specific. There are a few built-in ones, like: Create and Edit (no Delete), etc., which may suffice (though some files/tables require more fine tuning). Then there are a lot of possible combinations of settings if you use Custom on the choices. There's also the choices on the right side; Printing, Exporting, and last but not least, Available Menu commands (do not give them All, as it allows Replace Records, a very dangerous command, as well as Delete All Records).*

So there is no way privilege sets could transfer across files [ I spoke too soon; never say never]. If you stick with the simple built-in choices it should go pretty quickly. But you'd best learn a bit more about those settings, 'cause you'd hate to have edit them ALL afterwards.

If you remove [ ] Export for example, it also disables Copy All Records. There is also the possibility to have any particular script [x] Run with Full Access privileges, to override restrictions (within that file).

*Unless you're going to create limited Custom Menus, which is a whole 'nother area; requires FileMaker Pro Advanced.

Edited February 13, 200818 yr by Guest

Now we were testing this out yesterday and it appears we would then need to create the permission access to each database individually, is there a way we can create the permissions we want on one database, and propagate the permissions to all databases on that server?

You can use the FMRobot to copy Privilege Sets among files. However you still have to set up Accounts. Check it out

at the New Millennium web site.

You have a mess here, I'd say.

Steven