adyf Posted March 9, 2011 Posted March 9, 2011 Does anyone have any clues as to what causes the below error? I cannot modify any records within that table although the strange thing is I have some of those fields related in another table and can modify them from there. I haven't set up any security or exclusions to my knowledge.
Lee Smith Posted March 9, 2011 Posted March 9, 2011 Can you open the file using the Full Access privileges
adyf Posted March 9, 2011 Author Posted March 9, 2011 Can you open the file using the Full Access privileges I believe the file is opening as Admin with full access privileges.
Lee Smith Posted March 9, 2011 Posted March 9, 2011 It does not sound like it is. Close the file and hold the Option key down when opening it. Or. Open File >> Manage >> Security (if you can)
comment Posted March 9, 2011 Posted March 9, 2011 It looks like a custom validation message - not related (at least not directly) to privileges.
adyf Posted March 9, 2011 Author Posted March 9, 2011 It looks like a custom validation message - not related (at least not directly) to privileges. Problem solved although it lends itself to another question. It was a custom validation message that I had set up based on usernames of the users that I wish to be able to modify records. I needed to alter the validation calculation to Get(Username)= "XX". The strange thing is, the fields I was trying to modify didn't have validation set. Doesn't validation only affect the field that it is set up in or can it affect other unvalidated fields in the same table which appears to be the case here?
comment Posted March 9, 2011 Posted March 9, 2011 if you setup a field to validate "Always", it will kick in when you try to commit the record. I needed to alter the validation calculation to Get(Username)= "XX" Are you sure that's what you want to do? It doesn't seem very secure.
adyf Posted March 10, 2011 Author Posted March 10, 2011 if you setup a field to validate "Always", it will kick in when you try to commit the record. If I uncheck the 'Always' box the validation will it only kick in when I try to modify that field only? Are you sure that's what you want to do? It doesn't seem very secure. What would be a better way? I thought the Username identity was a good idea because it is unique (unless I get two 'smithj') and it is protected by company IT policy.
comment Posted March 10, 2011 Posted March 10, 2011 If I uncheck the 'Always' box the validation will it only kick in when I try to modify that field only? If it's not 'Always', then it's 'Only during data entry'. I want to be careful here, because different types of validation trigger at different times - but in any case, if the user has not modified the field, validation will not occur. What would be a better way? Through Accounts & Privileges. Also, UserName in Filemaker can be changed through the application's preferences - thus any user can easily circumvent this and pose as another user. Use the AccountName instead.
Recommended Posts
This topic is 5007 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 accountSign in
Already have an account? Sign in here.
Sign In Now