Re: SQL Date function question

Glad to hear you have it resolved.

One advantage to using something like Alan Campin's iDate (or your own
UDF) is that you can bury it into a view and not have to duplicate the
date conversion into every query. For example, if I do
CREATE VIEW ECHL97 AS (SELECT idate(hedte,*CYMD) as OrdDate, ...
Then in subsequent queries you can just shoot against that.

The only problem is that the sort/select performance isn't as good as
going against the raw date. You know, the old
select ... where hedte = ConvertDateToNumber(current date)
will outperform
select ... where ConvertNumberToDate(hedte) = current date

But your lousy MMDDCCYY stored date is pretty worthless for
sorting/selecting in any performance manner for any ranges. Oh, it may be
ok for one exact date but that's it.


Rob Berendt