The Original FileMaker Community
Business Templates - Demo Apps - Video Tutorials -Samples - Help - 46000 Member Forum

The Leading Filemaker Developer Tools

How Security Settings Can Break FileMaker Scripts – FileMaker Today


This is not as uncommon as you may think. What happens is that security protection is considered as an afterthought by the developer and/or project manager. So a developer starts to put in their security settings sometime before going LIVE with their FileMaker solution or shortly there after. They start to get reports from users that say that this button no longer works. Many times, the developer assumes the user must be doing something wrong. That script worked fine and hasn’t been touched it in ages.


How Security Settings Can Break FileMaker Scripts What has happened, is that you didn’t test the script when signed in at a particular security level. One of the settings in the security level is breaking your script. I do not know of any script or security debugger that will catch this for you. I wish I could lay out all the possibilities for you but I cannot. I will give you the two biggest ones that I’ve come across.


Ability To Edit A Record Turned Off

This will break scripts with the steps of Paste, Insert, Set and Replace for all field types except for global fields. Generally, you will get no blinking lights or warning sirens when the script is running. For script steps that use Paste or Replace, FileMaker will simply pass over the steps it cannot perform and you will be none the wiser. If you are pasting / inserting a calculated result or using the SET script step, FileMaker will generally give you an error dialog box of “Your password does not enable you to do this, or this file is not modifiable.” Of course, if your script has Set Error Capture On, you will not even get this dialog box. In fact, you may end up capturing the wrong error code.


Ability To Export Records Turned Off

This will break script steps that import from one file or table to the next. If you do not have the ability to export records, another FileMaker file will not be able to import that data into it. This will also break the script step of Copy All Records. This can be very troublesome if you are copy a set of records to use in a report or email message.


How Security Settings Can Break FileMaker Scripts Most of the above content was written when FileMaker 6 was the latest release. Although the situations are still relevant, those of us using a newer version of FileMaker have an advantage in the above situations. This is a small checkbox in the script to run with full access privileges. So if you click this check box, the script will run as if the user had no data or layout related restrictions and then go back to the users actual security settings when the script is completed.


=

More info about the author and FileMaker in general, contact me at This email address is being protected from spambots. You need JavaScript enabled to view it..


© 2008 – Dwayne Wright – dwaynewright.com


The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More

Privacy & Cookies Policy