Results 1 to 5 of 5
  1. #1
    Join Date
    Jan 2004

    Unanswered: Error in 2003 "invalid use of null (94)" a date field

    Hi -

    My company recently converted from Access 97 to Access 2003. Since the upgrade, I'm getting an error message when I try and enter a date in a date field on a form. I get the "invalid use of null (94)" error message.

    I've looked at the properties and the field is still correctly showing a short field as the data type...any ideas or suggestions?


  2. #2
    Join Date
    Sep 2005
    Bay Area CA
    Is there code attached to the form? If so, are you using a recordset (DAO?) Change the order of the references- bump DAO as high as it will go.

  3. #3
    Join Date
    Nov 2003
    An "Invalid use of Null" message means exactly that. A null value is placed where it's not acceptable which in your case is the date field.

    Handle this condition. See help on the Nz() function. If the error is based within a table then ensure the date field is permitted to accept a Null value. Check the Reguired property. If set to Yes then a Null value can not be placed into the date field.

    Self Taught In ALL Environments.....And It Shows!

  4. #4
    Join Date
    Jan 2005
    Nanded, India
    Even if the date field is set to Required = Yes , you are entering the value in this field. So there no question remains of Invalid value of null for this DATE field.

    I think there should be field(s) on the form (before entering date) which you set visible =false or kept behind some other bound / unbound text boxes and thiose are set Required = Yes and no value(s) are being supplied.

    View your table and check all the fields for Required property.


  5. #5
    Join Date
    Aug 2012
    Heredia, Costa Rica

    Lightbulb See my response to a similar question - Don't let it happen :-)

    See my response to a related query:

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts