Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7699 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

Does anyone know the boolean syntax for allow/disallowing access to specific fields? If you are editing a password, you can select either "All Fields" or "Limited..." for things such as browsing, editing, deleting. However, if you select limited you are supposed to enter some sort of boolean equation - the syntax for which is not mentioned! So if ANYONE has experience with LIMITING PASSWORDS TO ACCESS ONLY CERTAIN FIELDS WITHIN A FM DB, please let me know... thanks,

Matt

Outdoor Sportz

www.outdoorsportz.com

Posted

Hi:

Go to Access Privledges overview (File/Access Privledges/Overview). There you will see a list of your passwords. Select the password and then de-select the desired field in the Fields list.

Ken

Posted

The boolean expression is any valid Filemaker formula that returns a non-zero (true) value for records that the user is to access, and a zero (false) value for records that the user should not be allowed to access. So, if you have a field called "Access Level" and you don't want users to access records where Access Level contains the text "Top Secret" then use this expression:

Access Level <> "Top Secret"

  • Newbies
Posted

Thanks for the reply Ken,

this doesn't work for me though, ... i am not using any groups, and everything seems to be locked unless i use a group... are groups REQUIRED?

thanks again,

Matt

Posted

Groups are required to define access. You could just make one group, and assign all passwords to this group. Then you would be able to use it.

Although if this system will be used by many different people with different levels of access, I would highly recommend using groups, like in other systems. Even if you only had two groups: Administrators and Users.

Ken

Posted

You don't need groups to define access, but if you want to determine who is logged in by means of a script or calculation, you can't get the current password, but you can get the current group. So, this is just a roundabout way to find out who the user is. You can then set the record access in a calculation with this information.

  • Newbies
Posted

BobWeaver:

Thanks a lot for the syntax - very useful...

another question: is it possible to limit by field, versus by record, what a user can/cannot edit via this syntax?

thanks again,

Matt

Posted

I don't think field validation is a very good means to restrict field access, I would probably put any restricted fields on a different layout and then control access to the layout with a group access or a script.

This topic is 7699 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.