<div>
Do this: 
 
Dim sTag as String 
sTag = DLookup(&quot;Tag&quot;, &quot;LOCALtblCurrentUser&quot;) 
'/ now cycle through the controls: 
Dim ctl As Control 
For each ctl in Me.Controls 
&nbsp; ctl.Enabled = (ctl.Tag &lt;&gt;&nbsp;sTag) 
&nbsp; ctl.Locked = (ctlTag = sTag) 
Next ctl 
 
This will retrieve the value of the Tag field from your table and then cycle through each control on the form and set the Enabled and Locked values based on the value in that control's Tag property
</div>

<div>
Add a Me.Repaint before your permissions call. &nbsp;In the on open event, controls may or may not be instantiated yet. 
 
Or move your code to the OnLoad, but which point they all will be. 
 
Most use the OnOpen though because you can cancel it. 
 
Jim.
</div>

<div>
What is &nbsp;&quot;Me!Controls.Locker&quot;? I'm not aware of such an propery of the Controls collection. 
 
You need to loop explicitly over all controls.
</div>

<div>
Think that's a typo, should be &quot;Locked&quot; 
 
Jim.
</div>

<div>
which actually brings up the point of: 
 
1. Always use option Explicit 
2. Always compile frequently as you write new code. 
 
Jim.
</div>

<div>
If you want to use the code in more than one form, you need to generalize it AND place the PUBLIC procedure in a standard module rather than in the form's class module. 

<pre><code class="code-10 nolinks" id="code-20-41353261-1">Public Sub Permissions(frm As Form)
Dim sTag as String
Dim ctl As Control
sTag = DLookup(&quot;Tag&quot;, &quot;LOCALtblCurrentUser&quot;)
'/ now cycle through the controls:
For each ctl in frm.Controls
 ctl.Enabled = (ctl.Tag = sTag)
 ctl.Locked = (ctl.Tag &lt;&gt; sTag)
Next ctl
End Sub
</code></pre>
 
To call this code, use the CURRENT event. &nbsp;This gives you more flexibility because it allows you to control the locking based on data contained within a record should you need to. &nbsp;For example, I have an app that manages a drawing log for a steel company with several divisions. &nbsp;All the data is in the shared database and all authorized users may view it. &nbsp;However, updates are restricted to people from the division that created the job. &nbsp;So my code includes a lookup to the user's record to find his division and includes the division that created the job as an argument. &nbsp;The code then matches the parameter division with the employee division lookup when doing the locking. 
 
When you call the procedure, pass in a reference to the current form - 
Call Permissions(Me)
</div>

<div>
Scott: &nbsp;I had to change this line, ctl.Locked = (ctl.Tag = sTag), &nbsp;to ctl.Locked = (ctl.Tag = sTag) &nbsp;- &nbsp;It wouldn't compile without the dot. 
 
But then when I open the form I get &quot;Object doesn't support this property or method. 
 
******** 
So then Pat: &nbsp;I tried you code in a module. &nbsp;The form opens but the fields are not locked if the logged in user isn't Tag = 12.
</div>

<div>
Put a stop on the cntl.enabled line. &nbsp;Move the mouse over the ctl.Tag and sTag fields to determine their values. &nbsp;That should explain the locking issue. &nbsp;When the two values are the same, the expression returns true and that will set the enabled property to true. &nbsp;When the two values are different, the second expression will return true and that will set the locked property to true. &nbsp;If that is not logically consistent with your requirement, then specifically check for 12. 

<pre><code class="code-10 nolinks" id="code-20-41353421-1">Public Sub Permissions(frm As Form)
Dim sTag as String
Dim ctl As Control
sTag = DLookup(&quot;Tag&quot;, &quot;LOCALtblCurrentUser&quot;)
'/ now cycle through the controls:
For each ctl in frm.Controls
 If sTag &lt;&gt; 12 and ctl.Tag = 12 Then
 ctl.Enabled = False
 ctl.Locked = True
 Else
 ctl.Enabled = True
 ctl.Locked = False
 End If
Next ctl
End Sub
</code></pre>
</div>

<div>
I am so confused now I don't know where to put any code. 
 
What should go in a module? 
 
What should to in a form? 
 
Sorry I'm not getting it.
</div>

<div>
If you look back at my earlier post - 
 
The public permissions sub should go in a stand alone module - NOT in the form's class module. &nbsp;You want to be able to call the sub from ANY form. &nbsp;That is why I changed it to use an argument that references the form (Me) from which you are calling the procedure. 
 
The call to the permissions sub should go in the form's Current event for flexibility. &nbsp;Or, you can use the form's Load event but that will limit your options later.
</div>

<div>
Pat: &nbsp;Ok. &nbsp;I now have this in Module 1: 

<pre><code class="code-10 nolinks" id="code-20-41353472-1">Public Sub Permissions(frm As Form)
Dim sTag As String
Dim ctl As Control
 sTag = DLookup(&quot;Tag&quot;, &quot;LOCALtblCurrentUser&quot;)
 '/ now cycle through the controls:
 For Each ctl In frm.Controls
 ctl.Enabled = (ctl.Tag = sTag)
 ctl.Locked = (ctl.Tag &lt;&gt; sTag)
 Next ctl
End Sub
</code></pre>
And I have this in the form's on current event: 

<pre><code class="code-1 nolinks" id="code-20-41353472-2">Call Permissions(Me)
</code></pre>
But when I try to compile I get &quot;Wrong number of arguments or invalid property assignment&quot; on 
Call Permissions(Me)
</div>

<div>
Is module 1 a standard module or a class module? &nbsp;It needs to be a standard module. 
 
The syntax looks fine. &nbsp;Please post the db if possible.
</div>

<div>
Attached: &nbsp;Stripped down database. &nbsp; 
 
Log in as John Doe, password = 123 
 
From Main Menu go to [Client Data - EXISTING] 
 
The challenge: &nbsp;Every field on the data input form is tag - 12 therefore the only users that should be able read/write to the fields are either John Doe OR Case Coordinator. &nbsp;All other users should be read-only on the fields. 
 
There are going to be other fields with tags = 13, 14, 16, or 16 but this would get me started anyway. 
<a href="https://filedb.experts-exchange.com/incoming/2015/12_w49/1048588/Example.accdb" target="_blank" class="file-inline" title="Example (684 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Example.accdb</a>
</div>

Example.accdb

<div>
Note: &nbsp;I stripped out the suggested code because I could get it to work. &nbsp;That way you have a clean slate.
</div>

<div>
I did this in a Standard Module, as Pat suggested: 
 

<pre><code class="code-10 nolinks" id="code-20-41354430-1">Function LockControls(FormToLock As Access.Form)
 Dim dTag As Double
 dTag = DLookup(&quot;Tag&quot;, &quot;LOCALtblCurrentUser&quot;)

 Dim ctl As Control
 For Each ctl In FormToLock.Controls
 If Len(ctl.Tag) &gt; 0 Then
 If IsNumeric(ctl.Tag) Then
 ctl.Locked = CDbl(ctl.Tag) = dTag
 ctl.Enabled = Not CDbl(ctl.Tag) = dTag
 End If
 End If
 Next ctl
End Function
</code></pre>
I then called it like this in the Form Open event: 
 
LockControls Me 
 
And set the value of the Tag column in that LOCAL table to 12. When I opened the form, I could NOT modify any controls where the Tag property was set to 12. I was able to modify data in controls where there was no Tag value, or where the Tag value was anything other than 12.
</div>

<div>
Scott, this is backwards. &nbsp;Since the fields on the form have Tag = 12 then the users either John Doe OR Admin OR Case Coordinator NEED to be able to edit the fields. &nbsp;No other logged in user should be able to edit them. &nbsp;Just read them. &nbsp;(John Doe and ADmin being 11 need read/write always) 
 
How should the code be altered to accommodate this? &nbsp;If I didn't explain it well I apologize)
</div>

<div>
Then you need to specify your security scheme. We can't guess at it, and adding things after the fact (i.e. the concept of Admin and Case Coordinator) serve only to confuse the process. Also, we have no idea what an &quot;Admin&quot; or a &quot;Case Coordinator&quot; might be, or how they would be identified. You have to give us that information. 
 
With that said ... 
 
Are you saying that the number found in the Tag property is the highest value that can edit the control? So if you have a Tag value of 12, anyone with a value of 12 OR LOWER can edit that control? 
 
What about if there is NO value in the Tag property for that control? Can anyone edit, or should it be locked for all users? 
 
To modify the code: 
 
If you need it editable when the value is EXACTLY 12: 
 
ctl.Locked = Not (CDbl(ctl.Tag) = dTag) 
ctl.Enabled = CDbl(ctl.Tag) = dTag 
 
If you need it NOT editable when the value is EXACTLY 12: 
 
ctl.Locked = (CDbl(ctl.Tag) = dTag) 
ctl.Enabled = Not (CDbl(ctl.Tag) = dTag) 
 
If you need it editable when the value is LESS THAN OR EQUAL TO 12: 
 
ctl.Locked = Not (CDbl(ctl.Tag) &lt;= dTag) 
ctl.Enabled = CDbl(ctl.Tag) &lt;= dTag 
 
If you need it to be NOT editable when the value is GREATER THAN OR EQUAL TO 12: 
 
ctl.Locked = Not (CDbl(ctl.Tag) &gt;= dTag) 
ctl.Enabled = CDbl(ctl.Tag) &gt;= dTag
</div>

<div>
There are lots of ways to set up security and as Scott suggests, you need to come to a decision and define all your rules. &nbsp;I don't understand the concept of what you are trying to implement. &nbsp;We just did what you said you wanted. 
 
In one app, I need to control access to certain forms but it is an all or noting proposition. &nbsp;I don't need to control at the field level. &nbsp;In that database I have a table of objects, a table of users, and a table of user actions. &nbsp;Since everyone has read access to everything, I use the absence of a record in UserActions to mean that the user has only read permissions. &nbsp;Otherwise, the UserActions record will specifiy which action he is allowed. 
tblUserAction 
FormID (primary key part 1) 
UserID (primary key part 2) 
AllowAdd 
AllowDelete 
AllowUpdate 
 
So the form's BeforeUpdate and Delete events look for a record with the current form's ID and the userID. &nbsp;If it is found, the action flags are checked. &nbsp;If the user is not allowed the action he is attempting, the code cancels the action and issues an undo to back out the changes. 
 
If you also want to control reading, add a fourth action - AllowRead and check that in the form's Open event. &nbsp;I just ignored reads because unless you have to control them, adding a record for every form for every user can be tedious. 
 
Another way of using this method is to assign users to groups and create a GroupActions rather than a UserActions table. &nbsp;This will dramatically minimize your security management since you probably will have only a couple of user groups whereas you may have hundreds of users.
</div>

<div>
Scott, 
 
Again I apologize for not being 100% specific from the beginning. &nbsp;You suggestion: 
 
To modify the code: 
 
&nbsp;If you need it editable when the value is EXACTLY 12: 
 
&nbsp;ctl.Locked = Not (CDbl(ctl.Tag) = dTag) 
&nbsp;ctl.Enabled = CDbl(ctl.Tag) = dTag 
 
Is almost correct. &nbsp;If the field tag = 12 &nbsp;and if the logged I user has 12 in the tag field in LOCALtblCurrentUser then they need to be able to read/write to the field. &nbsp;BUT, also, if the logged in user has 11 in LOCALtblCurrentUser then that users needs to be able to read/write also. &nbsp;No other user other that 12 or 11 should be able to write. &nbsp;Should be read only. 
 
11 is to be read/write always.
</div>

<div>
<div class="content wysiwyg-content">
Maybe this won't work but I am trying to establish field security on a form using the tag in the property sheet of the fields. &nbsp;The user logs in via a login form and if the log in properly a number is written to a field named &quot;Tag&quot; in a table named &quot;LOCALtblCurrentUser&quot;. &nbsp;So for example the tag written to that user may be 12. &nbsp;This is working perfectly. 
 
But then on a form if the field Tag is anything other than 12 I want that field to be locked on open. &nbsp;(Or maybe it should be on load ?) 
 
Here is a public function I put at the bottom of the form code: 

<pre><code class="code-1 nolinks" id="code-10-28894070-1">Public Sub Permissions()
 If DLookup(&quot;[Tag]&quot;, &quot;LOCALtblCurrentUser&quot;) &lt;&gt; 12 And Forms!Controls.Tag = 12 Then
 Me!Controls.Locker = True
 End If
End Sub
</code></pre>
And here is the onopen event of the form: 

<pre><code class="code-1 nolinks" id="code-10-28894070-2">Private Sub Form_Open(Cancel As Integer)
 Call Permissions
End Sub
</code></pre>
But this isn't working. &nbsp;Can someone help?
</div>
</div>

Maybe this won't work but I am trying to establish field security on a form using the tag in the property sheet of the fields.  The user logs in via a login form and if the log in properly a number is written to a field named "Tag" in a table named "LOCALtblCurrentUser".  So for example the tag written to that user may be 12.  This is working perfectly.

But then on a form if the field Tag is anything other than 12 I want that field to be locked on open.  (Or maybe it should be on load ?)

Here is a public function I put at the bottom of the form code:
(CODE)
And here is the onopen event of the form:
(CODE)
But this isn't working.  Can someone help?

Trying to setup security level on form fields

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.