They don't. The function always accepts MMDDYY as it's input, and YYYYMMDD as it's output. It doesn't attempt to guess anything.

The formats, however, are really irrelevant to the example. The same example works just as well if it's DDMMYY for input. The point is that you don't have to code a separate function/procedure for every possible variable type.


On 4/20/2010 5:14 PM, hr@xxxxxxxxxxxx wrote:
Scott

how do your generic subprocedure "guess" the dateformat in your numeric
field in your example ??


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.