Young Padawan Posted November 25, 2004 Posted November 25, 2004 Besides having a field called "locked" and scripting, is there any other way to lock certain records in a table? I have an extremely complex database now and the thought of going back and changing scripts, creating locked/unlocked layouts, etc isn't very appealing.
Reed Posted November 25, 2004 Posted November 25, 2004 Why not have a field called "locked" and just limit edit and delete privileges to not allowed if the locked field is true.
Søren Dyhr Posted November 26, 2004 Posted November 26, 2004 Jmo has uploaded such a template at: http://www.filemakerpros.com/LOKFIELD.zip --sd
Computer Geek Posted November 27, 2004 Posted November 27, 2004 I have a large database and I found the method Reed posted is very efficient.
Edward Newman Posted December 3, 2004 Posted December 3, 2004 I have a similiar situation with invoices and propsals in our Biz Mgmt Sys. The problem is that when you have hundreds of fields, setting up the validations is a pain and not easy to set up a 'override' option for. There isn't a simpler way to lock a record?
stevie.at Posted April 30, 2005 Posted April 30, 2005 Validation "on record level" is what I'm looking for...but still can't find. So how is this supposed to work?
LaRetta Posted June 5, 2005 Posted June 5, 2005 Hi Stevie, Ed, I saw this thread when I was moving them. By locking any one field in a record (either via script inserting a 1 in a Lok field or by calculation depending upon multiple criterias), you can restrict access to ALL fields using extended privileges (as explained above). This determination must be made at some point; otherwise, how will system know when to restrict access to the record (which is simply all of it's fields)? Just in case you (or someone) still wants to know this process, try this Edit - Limited - Prvileges link . I explained it step by step. I use it to heavily protect posted, month-end records. When my records receive the date posted, extended privileges locks all fields. If you start with the proper 'template' privilege set, it does the work for you. Then you simply specify those fields (if any) the User IS allowed to still modify after the record is 'locked'. Field locking IS record locking - you just lock all fields in one whack. LaRetta
Recommended Posts
This topic is 7113 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