I can understand the logic for converting your input date to string or
number and using that to compare against the file data, and how that may
even be a better performer.
However, my feelings initially lean towards converting the data to true
date fields. And there's nothing stopping you from using strange dates
(like the date of the Massacre at Wounded Knee) for those special dates in
the old system of all sevens or some such thing.
I can understand a large bit of reluctance of doing that, especially if
the dates are in a vendor package. In that case my suggestion would be to
use a UDF to do it instead. Now, how you do the conversion in the UDF is
up to you. The beauty of the UDF is that it can also be buried into a
view so that user's queries become a breeze.


Rob Berendt

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-2024 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.