RE: SQL0181 and the IBM Date Window... -- 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: SQL0181 and the IBM Date Window...
From: "Cassidy, Alan" <CassidyA@xxxxxxxxxx>
Date: Mon, 17 Jul 2006 18:08:13 -0400
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Q... does anyone have any suggestions on how to convert a 7 digit long julian 
date (passed as an integer) using SQL where we could put it into a function 
like this?

A... I once had a database with almost all 7-digit dates. If they are numeric 
(that's how most of the shops I've worked in have them), you can just use this 
expression to get an 8-digit date:

CCYYMMDD = CYYMMDD + 19000000

--Alan

As an Amazon Associate we earn from qualifying purchases.

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.