Julian Dates

D

Dave Ruhl

In Access 2002 I am linking to a Paradox table that
stores dates in a different format. It is in the format
of a number (38170 for example). From my years working
with Visual FoxPro I think this is called a Julian Date,
and I'm pretty sure VFP had a function to convert it to a
real Date format. Is there a way to convert this date in
Access ? Thanks...
 
A

Albert D. Kallal

The number used in Paradox is likely some arbitrary starting date (and,
no..it has nothing to do with Julian dates).

Often, the developers choose 1 as some favorite date (first kiss, or perhaps
birthday of their daughter, often, the first day of when coding started is
also used). For example, in the pick system, to day is 13338. It turns out
this date is the number of days since the first pick system was designed (at
TRW for the military). If you go back 13338 days, you get Jan 01, 1968 (and,
that date is consider the birthdate of the pick operating system).

In windows, today is 38175

in windows 1 is 12/31/1899 (I guess they out of the blue decided to use this
date. Likely, it makes subtracting a bit easier, since 2 is = 01/01/1900).

Since 38170 is only 5 days ago 07/02/2004 , then it sounds like the number
is the SAME as windows.

You could try creating a quick query, and use:

DateF:cdate([thatDateField])

I think the above will do the trick.

Just try the cdate() function (covert to date) and see what you get.
However, it seems that in the linking, or setup, ms-access was NOT informed
that this is a date field..and you should not have to convert. Anyway..give
the above a try.

If the number is not right, you simply just need to design a function to
convert from one system to another. (in the case of pick dates..I just have
to add 24837 days to convert between each system) (so, I could write a
custom function and use that in place of cdate()).
..
 
J

John Vinson

in windows 1 is 12/31/1899 (I guess they out of the blue decided to use this
date. Likely, it makes subtracting a bit easier, since 2 is = 01/01/1900).

Actually I understand this was for compatibility with Lotus123. The
developers of Lotus evidently did not realize that 1900 was NOT a leap
year, and intended January 1, 1900 to be day 1. In fact, this threw
all dates off if you recognize that there was no 2/29/1900, so to keep
from having to redo millions of spreadsheets they just moved the
starting point.
 

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

Top