Bad Dates - 1/0/1900

[DBFIN]

I've extracted data from a Wintam accounting software and exported the data in a csv file format. Some of the dates show up as 1/0/1900 in the csv file. I've linked to the csv file and created a MS Access table. The 1/0/1900 dates in the table appear as a value other than 1/0/1900, it appears to default to the value of the nearest other date field.

Do you know why the 1/0/1900 dates get converted to a different value ?

 

[Alansidman]

Take a look here

http://www.wilsonmar.com/datepgms.htm#JulianDatez

Alan

 

[DBFIN]

Thank you for informing me about this resource. This certainly has pointed me in the right direction, however I am still struggling to convert the 1/0/1900 dates.

 

[namliam]

1/0/1900 is not a valid date thats why it gets converted...

 

[DBFIN]

I was in the process of researching this further and came to the same conclusion. I discovered that we had several valid transactions from the "transaction" database that were trying to join fields from another "policy" database via a common customer number. The corresponding record from the "policy" database had been deleted by the end user after the transaction was created, so the date field was appearing as a / /, an invalid date that converted to 1/0/1900.

Thank you again. You certainly helped resolved the problem and I appreciate it !!

 

[namliam]

Well.. in actuallity you could interpert this as day 0 of January 1900 or ... 31 december 1899...

Basicaly an empty date or 0 if you want to represent a number.