# Locking FileMaker Fields

**URL:** <https://the.fmsoup.org/t/locking-filemaker-fields/4169>\
**Category:** Lounge (Discussions)\
**Tags:** user-interface\
**Created:** [July 4, 2024, 9:51pm UTC](https://the.fmsoup.org/t/locking-filemaker-fields/4169 "2024-07-04T21:51:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tonywhitelive](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/tonywhitelive/32/208_2.png) [@tonywhitelive](https://the.fmsoup.org/u/tonywhitelive)\
**Post date:** [July 4, 2024, 9:51pm UTC](https://the.fmsoup.org/t/locking-filemaker-fields/4169/1 "2024-07-04T21:51:15Z")

</div>

Locking Fields is a useful feature for a variety of use cases...

Transaction tables like, Orders, Invoices, CashReceipts, Banking, etc. can have Fields "Locked" using Field \> Validation after all, or part of, the transaction has occurred, so that even a [Full Access] account can NOT accidentally modify the data in those Fields. Please note that the ability to Unlock is a Privileged operation (a topic for another time).

Let us use Banking records of type check as a simple example where the transaction has multiple milestones:

- After a check is "in the mail" the Amount, DateOfTransaction, etc. Fields can be locked
- When the check is reconciled agains a bank statement, the Account, StatementCode, etc. can be "Locked".

For this use case, we will need more than one "Locked" field, Locked\_1 and Locked\_2. See image below.

Here is an interesting question: How would you visually identify the fields that are "Locked" to the user effectively and efficiently?

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/b/b9036a838b09dab8aabb527c9a2edf48a498dad9.jpeg)

---

<div class="post-metadata">

**Author:** ![rivet](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/rivet/32/1727_2.png) [@rivet](https://the.fmsoup.org/u/rivet)\
**Post date:** [July 4, 2024, 11:48pm UTC](https://the.fmsoup.org/t/locking-filemaker-fields/4169/2 "2024-07-04T23:48:49Z")

</div>

Something like a disabled field in bootstrap would be my approach

 ![IMG_5581](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/c/ca8d00a6b0ba7739947927be9ef27d39d27dfa3d.jpeg)

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [July 5, 2024, 6:58am UTC](https://the.fmsoup.org/t/locking-filemaker-fields/4169/3 "2024-07-05T06:58:40Z")

</div>

> [@tonywhitelive](#):
>
> How would you visually identify the fields that are "Locked" to the user effectively and efficiently?

A softer colour is usually used for text that isn't interactive.

---

<div class="post-metadata">

**Author:** ![tonywhitelive](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/tonywhitelive/32/208_2.png) [@tonywhitelive](https://the.fmsoup.org/u/tonywhitelive)\
**Post date:** [July 7, 2024, 4:00pm UTC](https://the.fmsoup.org/t/locking-filemaker-fields/4169/4 "2024-07-07T16:00:08Z")

</div>

Thanks all,

For now I am going with a Fill of EEEEEE as the standard as it:

- Gives you more visible change that text
- Works even on a field that is both empty and locked
- Works on a field with text of different colors

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/d/d92a2edd59b8321845aa029db3d25058f2de7602.png)