× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



<snip>
Of course, you have to keep using a sliding scale on that huddle format,
limited to 100 years. Otherwise you'll get more than one join on any
MMDDYY join.

So, if you desire to use this huddle format to convert dates ranging from
birthdates of your most senior employees, all the way up to the end of
depreciation of a new building you just built you may find it unusable.

Nope, not for me.

Granted, if you're still using any MMDDYY dates then you <expletive
deleted>
Joining on an 8 digit to convert to a mmddyy, just for display purposes,
may be ok, even if you go over the 100 year scale. It's joining on the 6
digits you'll shoot yourself in the foot.


Rob Berendt

</snip>

the UDF you've recommended, has the same problem (or both don't have any).
Just try to join a table with an alpha date to another table with a numeric date, try your function and my recommendation and you will see dramatic performance diffrences.
BTW: my recommendation is coming from an installation with hundreds of millions of records for single tables...

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.