Mandatory Data Entry In Field Before Moving to Another Field

[meena]

Below is my code... But it does not seems to work :-(

1. If my booking ID is blank It displays the error message and enters the next field. Goes through the validation of the next field pops up the message. displays the ID error message and sets the cursor to the last field my form.
2. I have added in the validation rule = Is Not Null and Validation text = ooking ID cannot be blank
3. Changed the code from txtbookingid.Setfocus to SendKeys "+{TAB}"
4. Similar code for other field validation works fine, but for this one I am stuck.

Not sure where I am going wrong.


Private Sub txtbookingid_LostFocus()
Dim db As DAO.Database
Dim rs As DAO.Recordset
Dim MyVal As Long
Dim strSql As String

Set db = CurrentDb()

If Me.txtbookingid = "" Or IsNull(Me.txtbookingid) Then
MsgBox ("Booking ID cannot be blank")
SendKeys "+{TAB}"
Else
strSql = "SELECT BookingID,StartDate,EndDate,NoAdults,NoChildren " & _
"FROM Booking_Header " & _
"WHERE BookingID = " & Me.txtbookingid & "" & _
"AND BookingStatus NOT IN ('COMPLETED','CANCELLED')"

Set rs = db.OpenRecordset(strSql, dbOpenDynaset)


If rs.RecordCount = 0 Then
MsgBox (" Please enter the customer details before planing the Itinerary")
Me.txtbookingid = ""
SendKeys "+{TAB}"
Else
Me.txtstartdate = (rs!Startdate)
Me.txtenddate = (rs!Enddate)
Me.txtNA = (rs!NoAdults)
Me.txtNC = (rs!NoChildren)
End If

rs.Close
Set rs = Nothing
Set db = Nothing

End If



End Sub

[Bob Fitz]

IMHO it is best to put validation code in the before Update event which can be cancelled.

[azhar2006]

An example of a professor (ItsMe )
Under the name (Parts Issue)
This is a copy of which he was a very nice
not leave the field empty

[meena]

My form is an unbound form. I want to validate each field and ensure proper data is entered before the user jumps to the next field. When my I open my form, my code is not triggered and moves to the next field. However if I key in something & clear it then it recognizes it as null and triggers my code. Hope to have some guidance.

Private Sub txtstartdate_BeforeUpdate(Cancel As Integer)


If IsNull(Me.txtstartdate) = True Or Me.txtstartdate = "" Then
MsgBox ("Please enter the Itinerary Startdate before you proceed")
Cancel = True
ElseIf Me.txtstartdate <= Me.txtbookingdate Then
MsgBox (" Trip Start Date should atleast be 20 days after Enquiry date ")
Cancel = True
End If


End Sub

[meena]

IMHO it is best to put validation code in the before Update event which can be cancelled.

I did try but doesn't seem to work.

My form is an unbound form. I want to validate each field and ensure proper data is entered before the user jumps to the next field. When my I open my form, my code is not triggered and moves to the next field. However if I key in something & clear it then it recognizes it as null and triggers my code. Hope to have some guidance.

Private Sub txtstartdate_BeforeUpdate(Cancel As Integer)


If IsNull(Me.txtstartdate) = True Or Me.txtstartdate = "" Then
MsgBox ("Please enter the Itinerary Startdate before you proceed")
Cancel = True
ElseIf Me.txtstartdate <= Me.txtbookingdate Then
MsgBox (" Trip Start Date should atleast be 20 days after Enquiry date ")
Cancel = True
End If


End Sub

[Missinglinq]

Why are you using a Unbound Form? Using Unbound Forms does away with the primary reason for using Access, which is to take advantage of it ability to facilitate the RAD (Rapid Application Development) of Databases!

With Bound Forms, Access does the vast majority of the heavy lifting; with Unbound Forms the developer has to write code for just about everything, even the most mundane tasks. Several developers I know, experienced in Visual Basic database development, as well as Access development, estimate that development, using Unbound Forms, by highly experienced developers, takes two to three times as long, using Unbound Forms, as it does when using Access and Bound Forms.

In short, there is very little that can be done using Unbound Forms that cannot be accomplished with Bound Forms, and usually done with much less work!

Anyone who insists on using Unbound Forms, would be far better off using a straight VB or C++ front end with a SQL Server or Oracle back end.

• You can create an EXE file which gives total protection to your code/design
  
• You can distribute the db to PCs without a copy of Access being on board
  
• Your data security is far, far better than anything you can do in Access

It should be added that there are a few very specialized reasons for using Unbound Forms in Access, for general data entry of Records, but they are very specialized, and situations that a newbie is very unlikely to come upon. I've been writing Access apps for well over a decade now, and have never had the need for using Unbound Forms for general data entry.

Linq ;0)>