I am using FMP 6.04 on a Mac and I hope someone can help me set up a conditional RLA but with a "variable" condition (ie I want to stop "accidental" editing (changing) records in an invoice file). I have been able to set up restricted access based on password so that once the invoice has been paid out, the record is uneditable by that password user. However I would like that person to be able to "deliberately" edit if necessary by using a password or some other means to access the record again.

I have tried setting up an editing layout with a password field but I can't make it "overwrite" the editing restrictions properly. I have tried calculations in the editing restriction dropdown of the password access privileges to limit editing to records where the user with that password and the invoice has been paid out OR if the password entered into a dialogue box on the editing layout matches a password held in a hidden field.

What I would like is for the user to go to the editing layout in a locked record, type a password and unlock the record. I'm not after high security, just protection from accidental changes, and I don't want to have to get an administrator to come in and make the changes.

Can someone help with this - it would be much appreciated.

Cheers, Murray

Solved it by allocating a numerical value based on whether the account had been paid out or not, and another based on whether the entered password equals the stored password and based limitation to editing on the value of the sum of these two values, so the editability of the record could be changed dynamically by entering the correct password.

Much simpler than I thought really.

That is a question I have had for a long time. Is there a way to have a password entered and then compare it to their filemaker password. I could not find any function to perform this. It is easy to get current user or account but not password.

I don't think there is any way for the password to be obtained from within Filemaker - it would be a huge security problem if it could be done.

In FMP 6 you could allocate each separate user a separate group and allocate only one password to each "group" and not allow them to change it, then using Status(CurrentGroup) you would know who the user was and therefore their password, but you would have to have the passwords stored in fields within the table and this would again be a security problem.

I realize it would be a security concern. But I don't want to know the password just have person enter their password. If it is correct then the script would proceed, if not the script would give an error. That way you could have electronic signature as secure as the logon process.