Re: m/d/yyyy string to yyyymmdd decimal in SQL -- MIDRANGE-L

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

Subject: Re: m/d/yyyy string to yyyymmdd decimal in SQL
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Mon, 7 May 2018 11:36:50 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I love iDate. I don't think, though, that I've used *MDCCYY with no slashes. I just tried it. Here's a fun one:

iDate('1282018', '*MDCCYY') = 01/28/2018.

So much for December 8th. :) But then again, that's why we either use zeros or slashes.

Slashes are optional.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: m/d/yyyy string to yyyymmdd decimal in SQL , Rob Berendt

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.