× 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: Storing dates - revisted...
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Mon, 21 Sep 1998 14:03:16 -0400
  • Organization: commsoft

On Monday, September 21, 1998 11:29 AM, Chuck Lewis 
[SMTP:CLEWIS@IQUEST.NET] wrote:
> More questions on date storage !
-snip-
> It seems to me that YYYY/MM/DD is the better way to go (more
> straightforward) as century really is "clumsy" )have to remember where 0
> and 1 start and stop)... ??????/

All our new RPG development is storing dates as YYYYMMDD only because we 
have back-level customers, and we started this effort on V3R1, but there 
are still lots of legacy files using YYMMDD.  Those legacy files are 
getting converted to CYYMMDD (not my choice).  Synon/2E (aka Cool) uses a 
similar format to store dates.

If I were doing work for V4R1+, I would use native date data types.  This 
is what I'm using for my own tools, etc. on our V4R2 box.  They are very 
compatible with SQL and therefore ODBC and various PC products...

Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.