Using Nulls on Beforeupdate of form and Exiting w/o errors

[Researcher]

Hello,

I have successfully validated my form fields thru the use of Isnull statements in the beforeupdate event of a form, works great. However when I attempt to exit the form, my first field has the focus due to a tab stop 0. When leaving the form the field message appears "must complete this field prior to exiting form.
How can I disable the isnull check when exiting? I tried changing the focus but did not work. Any ideas would be appreciated...

Thank You,

Researcher

[missinglinq]

Validation data insuring that a field is populated is supposed to execute if the user tries to exit the form when the field on the current record is empty. Are you saying that the field in questioned has data but the message is appearing anyway?

You need to post your Form_BeforeUpdate sub so that we can look at it.

BTW, the first field having focus when you exit the form is not because it has a Tab Stop of 0, that's just coincidental.

Welcome to Bytes!

Linq ;0)>

[Researcher]

No, Let me explain further. After data is entered into the form and the record has been saved to table, the form clears and awaits a new record entry, however when attempting to exit the form thru an exit button, the validation check occurs because of no data in the field or fields. I can still exit the form, but without viewing those validation error messages. How can I exit the field w/o viewing the messages and still have field/form validation w/o null entries?

I realize the tab index number is only valid if you have a tab stop, setting the focus to that respective field controls the first field assigned.

Here is the code in the beforeUpdate event of the form:

 
Private Sub Form_BeforeUpdate(Cancel As Integer)
 
   If IsNull(Me.Events) Or Me.Events = "" Then
        MsgBox "You must Select an Event for this field ", vbCritical
        Cancel = True
        Me.Events.SetFocus
      Exit Sub
   End If
 
   If IsNull(Me.NoofCalls) Or Me.NoofCalls = "" Then
        MsgBox "You must enter the number of calls for this event, if no event enter zero, the field cannot be blank", vbCritical
        Cancel = True
        Me.NoofCalls.SetFocus
      Exit Sub
   End If
 
   If IsNull(Me.BoxOfficeCalls) Or Me.BoxOfficeCalls = "" Then
        MsgBox "You must enter the Box Office Calls, if no event, enter a number greater then zero, otherwise enter a zero, the field cannot be blank", vbCritical
        Cancel = True
        Me.BoxOfficeCalls.SetFocus
      Exit Sub
   End If
 
   If IsNull(Me.Operator) Or Me.Operator = "" Then
        MsgBox "You must enter an operator name, the field cannot be blank", vbCritical
        Cancel = True
        Me.Operator.SetFocus
      Exit Sub
   End If
 
   If IsNull(Me.Shift) Or Me.Shift = "" Then
        MsgBox "You must enter the operator's shift, the field cannot be blank", vbCritical
        Cancel = True
        Me.Shift.SetFocus
      Exit Sub
   End If
End Sub

[NeoPa]

The point here is that if you close the form with pending amendments to the data, then it saves those changes away for you. Not good to lose the validation for the convenience of exiting quickly.

I would consider using Me.Undo in your Exiting code before trying to exit. That way it assumes any changes should be aborted rather than saved.

Does this make sense?

[missinglinq]

After data is entered into the form and the record has been saved to table, the form clears and awaits a new record entry, however when attempting to exit the form thru an exit button, the validation check occurs because of no data in the field or fields.

The validation checks in the Form_BeforeUpdate will not occur simply because a "blank" new record has been displayed. The BeforeUpdate event will only fire if something has been entered into at least one of the fields, by either physically entering the data, or by assigning data to a control on a new record via code, such as assigning the current date to a field or assigning a generated ID number to the record..

If you have something like this coded, doing as NeoPa suggested, in your Exit code, with

If Me.Dirty Then Me.Undo

should solve the problem.


You might also check your code and make sure that you haven't put code in the OnExit or LostFocus event of a that first textbox you mentioned in your original post. Even on a new, non-dirtied record, code in either of these events will be fired when closing the form.

Linq ;0)>