get(layoutaccess) in find mode

[rossinin]

Hi,

I have a database running on a server in filemaker 8.5 and have the following problem. There are many users of the database and a small set of priviledge sets among them. I have set scripts up so that when a user tries to access a layout they don't have access to, it takes them there, they do see the "no access" gray screen in the back, but are immediately shown a dialogue box which tells them they have no access to that page and sends them back to the main page of the database.

However,when I go in (as the full access user)and I enter find mode and try and go to another layout, i can see the other layout in the background, but i get that same error message (that i created in the script to only work when get(layoutaccess) is 0 )and it doesn't let me go. When I leave find mode, everything works normally.

Essentially, somehow, in find mode, it is seeing my layoutaccess as 0 when it is not.

Any help with this would be greatly appreciated.

my script is:

got to layout

If get(layoutaccess)=o

Show Custom Dialogue (no access)

go to main menu layout

Thank you.

NR

[CobaltSky]

Hi rossinin,

First, let me say I can't reproduce the problem you have described. I opened a test file in FileMaker 8.5 and created the following script:

Enter Find Mode [ ]

Go to Layout [ “TestFile02” (TestFile) ]

If [ Get(LayoutAccess) = 0 ]

[color:#ffffff]..Show Custom Dialog [ Message: "no access"; Buttons: “OK” ]

[color:#ffffff]..Go to Layout [ original layout ]

End If

Enter Browse Mode

When I run the script while logged in with [Full Access] I don't see the "no access" custom dialog, but when I log in with an account that has no access to *records* via the TestFile02 layout, I do see the message. IOW the script I created works as I would expect it to.

I also double-checked the value returned by the Get(LayoutAccess) function and it returned 2 under the [Full-Access] account in both Browse and Find modes on the machine I tested on.

I suspect there is something else going on that is causing the problem you are seeing, but I'm afraid what it might be is not obvious from your description.

That aside, it would probably be a better use of scripting to freeze the window before navigating to the layout, then (if layout access is not available) navigate back to the source layout before displaying the dialog. That way the user does not have the (not so delightful) experience of gazing at an ugly gray screen. Just a thought. :wink2: