Does your script commit records after assigning a value to D_Set?
What storage option did you specify for D_Set?
Unless this is a global field, you have locked a single record by assigning a value to D_Set. Any other records in the table will still have D_Set = to 0 and thus will still be editable.
Yes it is a global field.
I'm assuming the script commits the record, because it does change D_Set from a 0 to a 1. If I go back and open the table it does display the 1 there. I would expect it not to let me change it back to a 0 or change the date... but I still can.... thus the confusion.
I'm a bit confused about "What storage option did you specify for D_Set?"
All help greatly appreciated!
The "storage option" is what makes the field a global field.
We routinely lock individual records in an invoice type system for two tables by setting a status field to "Printed" and I modify a global field as a way to unlock all the records in a table. So I know that this works.
So I'm guessing from you description since D_Set is a global field, that it has the "storage option" assigned correctly.
Still... hopeing someone can help figure out why my formula is not locking the record?
Compare what you have to this demo file. It auto-opens with a limited access password. If you enter a value into the global lock field and then click the layout background to commit the record, you cannot edit the name field until you "unlock" the field by clearing the lock field. To open the file in full access so that you can check the settings, you can hold down the shift (windows) or option ( mac ) key while opening the file and then use Admin with no password to open the file.