Help with error messages in access

[mcbride75]

Hi i am creating a database for a college Military Science department and have it just about done. I am encountering some issues with the debug phase. I need some error messages that are user friendly.

For instance:

I have a form that cadets will fill out. Information such as name, unit name, grade level, gpa, ect. ect.

When the teachers enter this into the database through the cadet form I want friendly error messages to appear if there is an empty field. Either when a save button is clicked or the text box loses focus. I have tried using the error codes (3314, ect.) but the code window will not return a code when I click save and an empty field is present, i do get the standard message. It does return the 3314 code when I click the "x" to close the form.

Any ideas?

[ADezii]

Hi i am creating a database for a college Military Science department and have it just about done. I am encountering some issues with the debug phase. I need some error messages that are user friendly.

For instance:

I have a form that cadets will fill out. Information such as name, unit name, grade level, gpa, ect. ect.

When the teachers enter this into the database through the cadet form I want friendly error messages to appear if there is an empty field. Either when a save button is clicked or the text box loses focus. I have tried using the error codes (3314, ect.) but the code window will not return a code when I click save and an empty field is present, i do get the standard message. It does return the 3314 code when I click the "x" to close the form.

Any ideas?

Place similar code to what I am showing you in the BeforeUpdate() Event of the Form, this way the Field Validation will be centralized, and regardless of which mechanism you may use to Save the Form, the Event will be fired and the Record will not be Saved until all Required Fields contain data.

Private Sub Form_BeforeUpdate(Cancel As Integer)
If IsNull(Me![Field1]) Then
  MsgBox "You must enter a value in <Your Field Name>", vbExclamation, "Missing Entry"
    Cancel = True: Me![Field1].SetFocus
ElseIf IsNull(Me![Field2]) Then
  MsgBox "You must enter a value in <Your Field Name>", vbExclamation, "Missing Entry"
    Cancel = True: Me![Field2].SetFocus
End If
End Sub

[mcbride75]

Place similar code to what I am showing you in the BeforeUpdate() Event of the Form, this way the Field Validation will be centralized, and regardless of which mechanism you may use to Save the Form, the Event will be fired and the Record will not be Saved until all Required Fields contain data.

Private Sub Form_BeforeUpdate(Cancel As Integer)
If IsNull(Me![Field1]) Then
  MsgBox "You must enter a value in <Your Field Name>", vbExclamation, "Missing Entry"
    Cancel = True: Me![Field1].SetFocus
ElseIf IsNull(Me![Field2]) Then
  MsgBox "You must enter a value in <Your Field Name>", vbExclamation, "Missing Entry"
    Cancel = True: Me![Field2].SetFocus
End If
End Sub

Alright. Now if I have 13 fields in the form would I just continue through to "field13"?

[missinglinq]

You could or you could loop thru the controls a variety of ways. Here's one example. It requires that you goto Properties - Other and enter a question mark (no quotation marks) in the Tag Property of each control you want to check. You can do this in one fell swopr by selecting all of the controls and changing the Tag property enmasse as it were.

Private Sub Form_BeforeUpdate(Cancel As Integer)
Dim Msg As String, Style As Integer, Title As String
   Dim DL As String, ctl As Control
 
   DL = vbNewLine & vbNewLine
 
   For Each ctl In Me.Controls
 
     If ctl.Tag = "?" Then
       If Trim(ctl.Value & "") = "" Then
 
        Msg = "'" & ctl.Name & "' is Required!" & DL & _
               "Please enter a value or hit Esc to abort the record . . ."
         Style = vbInformation + vbOKOnly
         Title = "Required Data Missing! . . ."
         MsgBox Msg, Style, Title
         ctl.SetFocus
         Cancel = True
         Exit For
         End If
      End If
   Next
End Sub
 

Welcome to TheScripts!

Linq ;0)>

[ADezii]

Alright. Now if I have 13 fields in the form would I just continue through to "field13"?

Another option is to set the Required Property of these 13 Fields in the Table to Yes. If the Required Property is set to Yes, when you enter data in a Record, you must enter a value in the field or in any control bound to the field, and the value cannot be Null.