I agree 100%... a lot of times you are dealing with more than one date conversion...

I use something that "came with" DB Web Query - a table called DATE_CONV. It's a lot faster than having a function.

Mine only goes to 12-31-2030


There is definitely a lot of value in iDate, and I'm comfortable
recommending it to anyone.

I think it's worth mentioning, though, that if you need to call a
function on every row in a large table, it may be worth using a date
conversion table instead, leveraging SQL's JOIN to do the
"calculation".

Building a date conversion table is pretty straightforward. Where I
work, I made one which also has things like Excel date, day of the
week, day of the week names, month names, and some other
awkward-to-calculate-on-the-fly stuff. I guess you could think of it
sort of like iDate, but pre-materialized into table form. I made ours
with 146097 records covering 1900-01-01 through 2299-12-31.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.