On Mar 4, 2011, at 11:06 AM, Stanley Weber wrote:

> I have a long FileMaker script that executes a "Delete All Records" script. The script works fine when I trigger it with my Full Access privilege set. When I trigger it as a typical user with no privileges to delete records, the script fails at that point. I suppose this makes sense, but how can I over ride this protection for a typical user?
> 
> I have "Run script with full access privileges" checked, but seems to do nothing.

Two questions:

1) Is the script with "Run with full access privileges" enabled the same script deleting the records?
Scripts do not inherit access privileges from calling scripts, so the script that does the deleting needs to have the RSWFA setting enabled.

2) Are the records being deleted in the same file as the script that is attempting to delete them?
The RSWFA setting does not traverse the bounds of the file. As such, a script in FileA would be able to delete records in a table defined in FileA, but not records from a table defined in FileB, even if those records from FileB are a viewed on a layout in FileA. You would need a script in FileB with the RSWFA setting enabled to delete FileB records.

3) (obscure) Is there a cascading delete on a relationship to records in another file?
Related to (2) above, if you are deleting records in FileA but there is a relationship to a table occurrence whose table is defined in FileB, and the cascade delete option is enabled on the relationship, then you will not be able to delete those related records if your non-script privileges to FileB don't allow you to do so.

Cheers,
-corn


Cornelius Walker
The Proof Group
http://proofgroup.com/