Dear FileMaking friends,

I'm trying to make a privelege set that denies a user access to previously made documents, yet allows them to edit new documents at will.

To do this, I've created a Locked variable, which begins at 1 (for a new file). When the file is written, it becomes 0 (false).

Under my custom record priveleges, for the given layout, I've granted users access to all fields. Then under the Edit side, I've made it limited base upon a boolean evaluation of the locked variable.

It seems however, that when I log in as the user, I'm not allowed to change data on any record, whether 'Locked' or un-'Locked'.

Any advice out there?

Thanks!

Edit:

Attachment posted below

Edited July 10, 200619 yr by Guest
Update

It would help to see the calcs/scripts involved.

My apologies, I was going to post this after I cleaned it up, but it should be workable. Sorry for the delay.

The Locked Records privelege set is the one I'm working on.

Guest has full access (just for the sake of simplicity) for the moment.

mscoles has Locked Records and no password assigned.

It says that "non-zero values are true (access is allowed)" and since the field is set to 1, I'm hoping it's read as a non-zero, but I'm unsure what's really going on.

Hope this can be of use,

Thanks a lot!

M

PMFv0.9_Empty.zip

Edited July 10, 200619 yr by Guest
File Update

Simply set the Edit privilege at the record level to No. See the article referenced at the top of the Security Concepts Forum page:

http://fmforums.com/forum/showtopic.php?tid/175633/

It explains this in great detail.

Steven

As to the specific calcs/scripts involved,

I use a set field to change Locked to 0 in a script.

Set Field [Locked; 0]

And to evaluate it, under the custom priveleges, Edit for that table is set to limited... where the only calculation it does is

Locked

Which, unless I'm mistaken evaluates locked in a boolean context, where 0 would restrict prilveleges and non-zero would allow editing.

Sorry, didn't see your post there. I'll see what I can find out.

If I missed a previous post, I'm extremely sorry.

Michael

No need for an apology. That article remains at the top of this Forum so folks can see it. When I have time, I'll do another one.

Steven