Hello,

We will be re-writing an fmp5 65 file solution and will likely end up with
about 5 files (modules) when finished.
In the previous solution managing security was a real nightmare. What type
of approaches can one use to centrally manage security in fmp8 when there
are still more than one file involved.

We want the user to have to login using Filemaker.
There will likely be 3 or 4 sets of privileges, one full for admin and the
rest different based on position.
If we choose to not use one central interface file but rather spread it out
across 4 or 5 files such as the business productivity kit solution from
Filemaker how might we proceed. Will I have to create the same user in all
5 files. If I do how do I make it so they login only once?

Any help appreciated. Perhaps a sample solution or book.

regards,

P.L

P.S Are we thinking wrong, should there be only one interface file? The
benefits are obvious but what would
be the pitfalls?

P. Lessard <lessardpeter (AT) hotmail (DOT) com> wrote:

I highly recommend you use External Authentication. But if for some
reason this is not an option....
Well, okay, but I've designed 3 FM7 solutions now using the central
interface file with separate data files (and External Auth for all of
them, Mac & Windows) and they work great. What a treat not to have to
import a bunch of data tables every time I make a change in a report or
data entry layout. I will never do a FM project again with
data/interface combined, unless for some reason I decide a single file
is optimum for some solution.

Yes, accounts and privilege sets with identical names must be created in
each file. (this is in any case) If you let users administer their own
passwords IN Filemaker, that means you have to SCRIPT changes through
out the files. And then comes the nightmare of upgrading, and somehow
trying to capture the changed accounts/passwords, or reverting everyone
back to a default password. I highly recommend you NOT follow the course
of:

A) Intermixed data and interface
B) Filemaker authenticated accounts for login

There is a product you might take a look at, built by one of the
foremost FM developers in the US, Vince Menanno.

http://fmnexus.com/accountmanager.html

This is built to administer multi-file accounts and privileges. Saw a
demo and it looked great. Vince used to be with Waves In Motion and
their products have always been rock-solid.

Lynn Allen
--
Allen & Allen Semiotics www.semiotics.com
FSA Associate Filemaker Design & Consulting

I haven't played around with this enough to recommend it, but I imagine
the following may work for you. Instead of having a password in every
file, just put the user accounts in the data file. All interface files
could automatically open using a low level user password that doesn't
allow access to layouts & scripts. When the user opens the solution,
they will be prompted for their name & password as soon as they try to
access any data.

It will still be a nightmare when you have to replace the data file so
decide for yourself how often that will happen. I recommend adding
spare fields!