Please see here a Security privileges set.

 

If I set a layout to <no access> that is easily done but notice that the records still show modifiable even though if you select it, it is grey'd out and you can't modify records 'via this layout if you don't have access to the layout.  

 

Now here's the fuss ... I cannot stand seeing <no access> on layouts with <modifiable> on records so I have to change the layout back to 'view only' so I can change the records to <no access> and only then can I specify the layout to <no access> so what displays in both columns is correct.

 

 

Sometimes it's the little things for us obsessive/compulsive personalities. 

I fuss the same way with changing the indexing on a text field ... I have to uncheck 'automatically create indexes' before I can change to All even though it greys out when selected.

Any advance news on upcoming FileMaker 14 ?

Upcoming FM14. Where did you here that?

New versions come out every 18 months or so and since 13 was the last, it would be good guess that 14 will be next.  However, 13 was released Dec 3, 2013 so I wouldn't expect 14 any time soon!

And of course, anyone that would know inside information about the next release is sworn to secrecy through a non disclosure agreement.

Any advance news on upcoming FileMaker 14 ?

 

How is this related to the topic of this thread?

LOL, I don't know but I'm glad SOMEONE responded on my thread. 

Dear Desperate on Saturday afternoon.

 

If I had been doing my job, I would have deleted Richard’s post. 

 

Instead, I tried to take a day off and got caught. ******* it.      

LaRetta, try adding a layout script trigger on layout entry if you get the <no access> navigate them to another layout they have access to with an error.

 

FileMaker's hierarchy when option A supersedes Option B settings on option B are dimmed out what ever they were set at and does not change it's value. So for the indecisive you switch back you option B's last known settings are preserved. 

 

Another example if you have auto entered turned on then had some crazy wacky formula in that calc box then turn off the check box the calc remains - for good or bad - i had a case where after using the DDR and Inspector i found a lot of field missing and other errors in these calc fields even though they aren't evaluated 

Hi Stephen, thank you for responding!

 

I must not have made my 'fuss' clear.  In my opening post, I show screen shot how we can set a layout to 'no access' but notice that the 'modify records via this layout' still show modifiable which is impossible since if a user can't access a layout, they can't modify records there.  It is true that it greys out but the fact that it still is checked 'modifiable' bugs me. 

 

That display should change to 'no access' as well (instead of simply greying out).  I always change the 'records' portion to 'no access' first and only THEN change the layout to 'no access' so it is logical and consistent looking to me.

 

Your ideas will be valuable in other instances so I really appreciate the input.  Or am I missing your suggestion somehow?

Another example if you have auto entered turned on then had some crazy wacky formula in that calc box then turn off the check box the calc remains - for good or bad - i had a case where after using the DDR and Inspector i found a lot of field missing and other errors in these calc fields even though they aren't evaluated 

 

Oh yes, and this bothers me as well so I remove everything.  :-)

FileMaker is trying to be thoughtful - and remembers prior settings on subordinate options - it keeps them when it can instead of disabling them and eradicating the values.

 

It comes down to personal OCD - and i know exactly what you mean - you the disabled option should "appear" to be most restrictive when its parent control is also set at its default - 

 

In a better world FMI should employ the HIDING trick to the UI elements so that when you choose NO ACCESS the other options just HIDE from view (keeping prior settings in memory) 

In a better world FMI should employ the HIDING trick to the UI elements so that when you choose NO ACCESS the other options just HIDE from view (keeping prior settings in memory) 

 

I really like that!!  It is these types of things that I try to learn from ... and employ in my solutions so that, for OCD users, they are happier.