Why doesn't locked field keep its property ONLOAD?

[Moah Scout]

Hi again!
I have a button on the Form to set allfields in a form to LOCKED. By setting the Event atOnClick_Event as:
Me.FieldName.Locked=True
When pressing the Button(Command67) all fields are LOCKED as EXPECTED. But if you Close the form and ReOpen it again you will find all form field are UNLOCKED and not LOCKED as before.
How should I keep it with its latest saved values and properties?

[ADezii]

1. Create a Public Variable in a Standard Code Module to indicate what the Locked Status of the Fields should be.
   

   Public blnFieldsAreLocked As Boolean

2. Create a Form Level Sub-Routine in the Form's Code Module that will Control the Locking and Unlocking of Fields on the Form.
   

   Private Sub LockFields(blnLock As Boolean)
   On Error Resume Next
   Dim ctl As Control
    
   For Each ctl In Me.Controls
     ctl.Locked = blnLock
   Next
   End Sub

3. To LOCK all Fields on the Form:
   

   blnFieldsAreLocked = True     'Set Public Variable to True
    
   Call LockFields(True)

4. To UNLOCK all Fields on the Form:
   

   blnFieldsAreLocked = False     'Set Public Variable to False
    
   Call LockFields(False)

[Moah Scout]

Thanks!
But I couldnt find the way out on where and why should I place the Code?
Give further details please?

[NeoPa]

From your question you seem not to realise that property changes to a running form are transitory, and do not cause the design of the form itself to be changed. I expect you need to consider the ramifications of changing the project design to handle a transient situation for an operator, as it isn't generally a good idea (with a little thought that should be pretty obvious).

If you absolutely need this to be remembered from one session to the next then you could consider storing the information that pertains to the state, and for which operator it's related to, in a table and reading the table when the form is opened so that the transitory state of the running form matches what you expect, without the form design requiring any changes.

[ADezii]

Hello NeoPa, I thought that the question only related to the Opening and Closing of a Form within the Current Session, and not from Session to Session. If I'm wrong, than the change can easily persist by writing the Locked State to the Registry or Hidden Table upon Form/DB Close, No?

[Moah Scout]

I couldnt catch your conversation!
How should it be handled then? Please!

[NeoPa]

Moah Scout:
But if you Close the form and ReOpen it again you will find all form field are UNLOCKED and not LOCKED as before.

ADezii,

From the text quoted from the OP, I believe Moah is saying he wishes changes to be maintained across sessions. If this were to be done, then using the Registry would not be recommended (bearing in mind this is an RDBMS after all) but a simple table (no reason for System or Hidden) could do the job. This would not be considered easy for anyone that wasn't pretty experienced, but could certainly be achieved (I'm sure you could manage it with your eyes closed).

The more important point of my post though, was about the advisability of handling anything this way. It is fundamentally unsound and can lead someone into uncharted territory further down the line (especially someone whose experience is clearly limited). This is why I urged for a reconsideration of the design. Would it be helpful to show someone how to get themselves deeper into trouble? It seems not to me.

@Moah,
Sorry to converse around you. For you I say forget about trying to do what you are doing that way. Give more consideration to exactly what you are trying to achieve and find an approach that doesn't involve the project reconfiguring itself on the fly. Perhaps if you shared what you're actually hoping to achieve, we could help in that area.

[ADezii]

@NeoPa - Points well taken, thanks.

[Moah Scout]

Thanks Adezii!
Let us do the technical parts of it.
How could this simple design be achieved?