If what asabi has said is all you needed to get going, then cool. If you really want to do something with that date field though, other than store whatever free text the text box had, you could think about something like the following...

You can use this example as is if you create a command button called Command1 and a Text box called Text1.

The idea here is to let VBA do all the hard work of parsing what is typed in the text box into a real date for you.

The new concepts you may not be familiar with but which you will hopefully find useful are the Date data type and the error handling.

Note that this example allows the user to type an string and recieve a date. Even if the user types 36711.25, they will get a valid date. This is because of how VB stored Dates for you which is another topic you could look up.

Try the example and see what date it comes out to...

Code:
Private Sub Command1_Click()
  ' decalre the variable myDate as the correct type
  Dim mydate As Date
  
  ' set up a local error handler
  ' this tells VB to note the error number but not to stop
  ' running if an error does happen.  Just go on to the
  ' Next command 

  On Error Resume Next
  
  ' cdate will try to convert anything to a Date
  ' if it fails, an error will happen
  mydate = CDate(Text1.Text)
  
  ' handle any error trapped.  VB stored any error in the 
  ' previous code as "Err".  You can look for that in the 
  ' VB help if you want to
  If Err <> 0 Then
    ' just make sure that date is set to some default
    mydate = 0
  End If
  
  'cancel the local error handler
  On Error GoTo 0
  
  ' show the user what was typed as a real date
  MsgBox "Date = " & mydate
End Sub
I hope it helps

Paul Lewis