Prevent Record Changes if checkbox property is true

[jdashm]

Trying to write some code that would prevent a user from making changes to a record unless the uncheck a field first.


The problem is that I can get a message box to display if the property of the field is true but it saves the changes anyway.
Here is the screenshot of the code I am trying to use...

Private Sub Form_AfterUpdate()
' After updating record in Production Delivery Board, checks to see if Packed checkbox is "Yes"
' If so, runs append query "qryAddShipRecord" to add new record to Shipping Log table
' If not, then just saves record
' Also prevents user from making changes to the current record if 'Packed' field is checked

If ysnPacked = True Then
MsgBox " You must uncheck 'Packed' field in order to make any changes to this record."
Exit Sub

ElseIf ysnPacked = False Then
With DoCmd
.SetWarnings False
.OpenQuery "qryAddShipLogRecord"
.OpenQuery "qupUpdateShipItems"
.SetWarnings True
End With

Else
Me.Dirty = False

End If
End Sub

[ItsMe]

What is ysnPacked? Is that the name of a control? What type of control?

[jdashm]

ysnPacked is a yes/no field that is visually a checkbox in that record on the form. It is the name of that control.

[ItsMe]

It does not seem that your code is firing. So, maybe you can be explicit with the control name in order to make sure you are evaluating the correct thing. Also place another message box just before that line for good measure. Of course, stepping through it in Debug Mode is always an option.

msgbox "Hello from the procedure! " & Me.ysnPacked.Value
If Me.ysnPacked.Value = True Then
    MsgBox " You must uncheck 'Packed' field in order to make any changes to this record."
    Exit Sub

 ElseIf Me.ysnPacked.Value = False Then
    With DoCmd

[ssanfu]

Private Sub Form_AfterUpdate()

I would think the form after update event would be to late to stop an update.
Maybe the form before update event to undo an entry if ysnPacked is true would be a better event????

[jdashm]

thanks... yes the "me." reference really helped and the message box confirmed that the field was checked or not.
I also moved the code to the "Before Update" event. It seemed to be executing better there.

However... the ysnPacked control could have been checked on previously.
The idea here is to prevent changes to a record if the user doesn't first uncheck the "ysnPacked" field which is fine but the code still activates when you are turning off and then on the ysnPacked field.
The code activates even when I turn on/off the ysnPacked field. I need the code to ignore changes to this field but still verify that the ysnPacked control is True or False.
Thanks in advance.

[jdashm]

Thanks for the response. I did realize the "Before Update" event would be the better choice.
If you could look at my previous thread post I could use some help finalizing how this code works.
Many thanks!

[ssanfu]

Would something like this work? Try and make changes if the record is locked...

[ItsMe]

Edit: I typed slow and did not see Steve's post. /edit

I am not even sure when the Form's Before Update or After Update fire. I would usually use the form's Unload event to cancel closing the form. But, I am not sure what the objective is here.

It seems there is a need to execute a couple of queries when a User is finished entering data into a form. Perhaps a button that executes the code would be a more practical approach. You could employ a MsgBox that asks for confirmation before running the queries. However, Users tend to go robotic and don't pay enough attention to the message boxes. So they might click OK, only to realize they did not want to run the update.

Maybe a pop-up modal form would be appropriate. The pop-up form would have a check box to save the record or a check box to cancel. Then the command button on the special looking pop-up form would execute the queries or cancel, depending on the checkboxes. Just be sure to commit the values in the previous form at the appropriate time.

[jdashm]

Thanks all for your responses. It is a huge help.
I am going with ssanfu's response. That seems to do what I need directly. It only allows editing of the record when the "ysnPacked" field is OFF. You nailed it!