Could someone clarify the precise action of this setting when calling a script in a remote database that has this setting enabled?

 

The specific scenario is as follows:

 

Database A and Database B are two separate Filemaker databases hosted on the same Filemaker Server 

 

User has [read-only access] in both databases, using an identical account name. This should mean he cannot create a record directly in any table in either of the databases.

 

Script 1 in database A has the "Run Script with Full Access Privileges" setting checked.  Script 1 includes a perform script step which refers to Script 2 in database B

 

Script 2 in Database B creates a new record in table Z, and has the "Run Script with Full Access Privileges" setting checked.  If the user has Database B open and runs script 2 directly -  it will create a new record in Table Z.

 

If the user opens Database A and runs script 1, does script 2 run as though the user had run it directly in Database B or is it in some way limited by the privileges in one or both of the databases?

 

I ask the question because I have a situation like this where the script B appears to fail if when the user is working with it, but using the users account and running under debug with Full Access privileges, it works correctly.

 

Any suggestions welcomed.

 

Brian

 

 

 

Since both scripts are set to run with full access, that's exactly what they will do.  How they are triggered (directly, or as a subscript) does not matter in this case.