I've deployed my (lightly) modded Complete2 solution.
I created additional identical user accounts for the Calendar, Media and Data files and gave them a limited access privilege set;
Records: Create and edit only
Layouts: all view only
Value lists: all view only
Scripts: all executable only
Printing on Exports off

I had to turn exports back on for users to be able to log in
All was OK until someone attempted to print a project sheet (button click performs a script similar to print bid) - no go.
I tried relaxing settings bit by bit but I'm just guessing and with three files to update each time it gets old pretty quickly. The upshot is that all my users are now on Full Access which is far from desirable

Any clues to a functional security setting would be most welcome

Hi there,

There are a few weirdnesses in security. First of all, in the Calendar file, users will likely need to be abel to delete records in the calendar rows table and the calendar interface table.

Also, exporting is required for all sorts of other things like...

Allow saving records as an Excel file.
Allow copying all records in the found set to the Clipboard.
Allow importing records from a FileMaker file.
Allow saving a copy of records.

But the big idea here is that real security-- what users can see and edit-- is dealt with in the data file. Though all files should have layout and script access reduced.

So you really only have one file to tweak the settings in, since your script and layout restrictions aren't causing the problems. I'd give this another shot, keeping the Calendar file more open (but prohibiting script and layout changes) and working on tightening the data file.

You can read up on this in FileMaker's built in help at Home > Designing and creating databases > Protecting databases

Hope that helps,

John