Could you create another layout based on the same TO that isn't locked down for a particular user. Then use some branching logic to go to this layout.
There's a function: Get(LayoutAccess) that checks to see what the user's access to this layout is. If this function returns 0, for the normal-course layout of the script, then go to the new layout.
I've never done this, but imagine it is possible.
EDIT: I just put together a quick demo file of it and this seems to work as I described above.
Go to Layout [Layout Restricted for user A]
If [Get(LayoutAccess) = 0]
Go to Layout [Layout open for user A]
I do imagine there's other ways. I need some caffeine
You can test this out on my demo file:
Admin / 1234 - full access
jbrown / 1234 - the "Access" layout is restricted for this user.
Access.fmp12.zip 67.2 K
What exactly is a "locked" layout?
Thanks for the input that is too complicated, has to be on the same layout.
Under File > Manage > Security > Privilege Set > Layouts > No access.
I thought of one solution if you can load during a script a different Privilege Set that grants all the rights needed. Is that possible or any other suggestion?
That should be overridden by the option to perform the script with full access.
Question: Are all scripts in the chain set to allow full access? Here's why: That setting does not pass to subscripts or scripts in other files.
Does the TO for the layout come from a table in the same file or from an external file?
Mike. As I read the documentation about the full access privileges, it only allows scripts to run with full access. there's no info that says it overrides the field and layout access privileges. I tested this out in a demo file. When going to a restricted layout, the script does indeed land on the restricted layout, but you get the "<No Access>" indication.
I must be missing something. (not impossible)
good point on the sub scripts, have to check. are you sure it overrights all security settings?
I thought I made the same experience
I don't know to what you are referring "TO"
yes the can come from any where same file external file does not matter.
Sorry, TO refers to Table Occurrence as in Manage Database Relationship graph.
Run with Full Access functions only in the file it was defined. It does not override security settings in external files.
Thanks I will try that out. thanks
Ah ha. I figured it out. You're right. The Full Access Priv check allows for the user TO GO the the layout and get data from that layout. Of course of that script stops at the restricted layout then you will be presented with the No Access grayed out layout, but you still get can get data from the layout.
Something new. . . .