![]() ![]() Therefore, it does not seem as important as the ability to validate upon viewing, editing and deleting a file. Perhaps this might not seem important as a new record has no data to be validated. The Ability to Validate a Record Upon Record Creation. has delivered this in FileMaker Pro 5.5, there are two noticeably missing features: the ability to validate a record upon record creation and the ability to run a script upon record browsing, editing, deleting or creating. ![]() You can use the pre-created file in the event that you encounter difficulty creating your own file.Īlthough FileMaker developers and enthusiasts have cried for record-level security features and FileMaker, Inc. I have included a pre-created "Test Delete.FP5" file so that you skip creating the file, and simply begin at Step 18 above. Either choose "Delete Record" from the Records menu, or select Command-E (Mac OS) or select CTRL-D (Windows).Įnabling record-level security for deletion protection in your FileMaker Pro 5.5 database solution is as simple as taking the above steps.Īuthor's Note: Whereas record-level security is tied to a password, entering "Test Delete.FP5" with the password "Master" will allow you to delete records regardless of the value contained in the "Delete It" field. Go to the record that holds a value of "Yes" in the "Delete It" field.Ģ3. ![]() ![]() Notice the validation error that appears. Either choose "Delete Record" from the Records menu, or select Command-E (Mac OS) or select CTRL-D (Windows).Ģ1. Go back to the record that holds a value of "No" in the "Delete It" field.ġ9. Create a new record and enter a value of "Yes" into the "Delete It" field.ġ8. In the existing record, enter a value of "No" into the "Delete It" field.ġ7. When prompted for a password, enter "User".ġ6. When prompted to enter in a master password, enter "Master".ġ5. In the calculation window that is presented, type in "Delete It = "Yes"".ġ2. Choose "Limited." in the pop-up menu next to the "Delete records:" label.ĩ. Enable the "Access the entire file" checkbox if it is not already enabled.Ĩ. Choose the "Access Privileges -> Password." command under the File menu.ĥ. Create one text field called "Delete It".ģ. Create a new, empty database called "Test Delete.FP5".Ģ. The following steps will lead you through creating a database, setting up two passwords (Master and User), entering a validation calculation for the Delete event, and testing to see the validation in action.ġ. Let's test to see record-level security in action. If it is false (""), the user will be prompted with "These remaining 1 record(s) could not be deleted because they were in use by other users or your password does not allow you to delete them." The event, then, would be disallowed. If the result is true (a "0" or ""), that event will be allowed. The calculation result must be Boolean that is, either true or false. Record-level security works by attaching a calculation to these three actions in the Define Passwords dialog box. Based on the password entered at startup, you can set different validation calculations that are triggered when a record is browsed, edited, or deleted. The newest, and perhaps most exciting feature of FileMaker Pro 5.5 is the ability to validate a record by calculation upon record viewing, editing, and deletion. TECHNIQUE FILES: Orders.FP5, Security.FP5, Test Delete.FP5 FileMaker Pro 5.5: Record-Level Security & oAzium Events 3.0 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |