I am really struggling with this and feel that I must have hit a bug.

I have duplicated the Data-Entry Privilege Set (PS).  I assign my new PS to a user and login as them.  All fine, my layout appears as it should, however, I get the option to 'Edit Layout'.

So, I return to edit my PS and change the Layout access from modifiable to view only.  After logging back in, I get what looks like 'Kiosk mode' (see first image).  Whereby, I have my layout open in the centre of the screen, surrounded by a black background that fills the screen and no menu bar.

Am I missing something fundamental?

Running on FMP 19.4.2.204 on Mac Monterey (12.2.1), but I can confirm the same effect happens on Windows 10.

The nearest I get to what I need (read-only) is by choosing the 'Data Access and Design' settings shown below.  But obviously with these settings the user can still edit the layout.

Edited May 12, 20223 yr by Crawfcol

I wasn't able to reproduce the problem using your description.

I started by duplicating the predefined [Data Entry Only] privilege set. Both the original and the copy have "All view only" selected for Layout access. That's already different from what you describe.

I then assigned the User account to this privilege set. Logging in as User I see nothing like what you describe.

FWIW, I am attaching my test file.

 

AccessTest.fmp12

Edited May 12, 20223 yr by comment

It is bizarre.  It is as soon as I change the Layouts permission to 'All View Only' the problem appears.

I just tried eliminating anything that was running in advance of the Layout opening (apart from the script below in a DB OpenScript) and get exactly the same effect.  It has to be a bug.  I have sent Claris a support case and await their response.

If [ Get(AccountName) = "user" ]

Go to Layout [ “Transactions (Read-Only)” (T2_Transaction) ; Animation: None ]

Show All Records

Sort Records [ Restore ; With dialog: Off ]

Go to Record/Request/Page [ First ]

Exit Script [ Text Result:    ]

End If

BTW thanks.  I tried your test file and it doesn't have the same issue.

Edited May 12, 20223 yr by Crawfcol

Have you been able to reproduce the problem in my file? Or in a new file? Or in any file other than the one you're dealing with now?

 

Yes I have now reproduced it in a separate file

Edited May 12, 20223 yr by Crawfcol

If you can reproduce the problem in my file, or in a brand new file, please post it here.

 

Unable to reproduce it in any file other than 2.  These files are basically copies (created some time ago), the first file I tried that experienced the problem is a copy of the first.

Looking more like a corrupt file

These files are hosted on a server and they are currently in use.  Once users are off the system, I'll take a backup and try and do a recover locally to see if it makes any difference.

Edited May 12, 20223 yr by Crawfcol

37 minutes ago, Crawfcol said:

Looking more like a corrupt file

That would be my preliminary conclusion too.

Or it could be something went wrong with your server (assuming you only see the effect on hosted files).

 

Edited May 12, 20223 yr by comment