Display of Null date vs. 12/30/1899



I have an Access 2007 project (.adp) that stores data in SQL Server 2005. In
two DateTime fields, null dates have been converted to 12/30/1899 12:00:00
AM. I understand that sending a zero or an empty string through VBA code
will cause this to happen. What I don’t understand is that on one client
machine the dates display in text boxes and reports as “12/30/1899â€, while on
another they display as null.

I can live with Null’s being stored as “12/30/1899 12:00:00â€, but is there a
machine-specific setting or anything else that would account for the
different displays of null dates?


It appears that the property of the Date Field in question was changed.
In the Table you will notice the (Required) property. If this is changed
from Yes to No or No to Yes what you are describing can occur. If I was you
I would write an Update Query that looks for Null Dates and insert a value.
Playing with dates in a Microsoft environment can be tricky. What I am
recommending is the easier way to go.

Good Luck



Toni, I'm sure that no column properties have changed. The two "bad" DateTime
fields both allow nulls. I may create an Update trigger that will change
12/30/1899 12:00:00 to Null- seems like it should work, but I may be chasing
down this issue for a while.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question