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


  1.  Home
  2. MIDRANGE-L
  3. May 2005

Re: "Date" fields

I have to agree with Rob. With the power of the newer boxes, these days imho, it's foolish to NOT use the date data type. It automagically converts itself to whatever format you like, and it's guaranteed to contain a valid date.There's never any confusion about what a date is supposed to look like, and for display purposes, all I need to do is %char(mydate:*USA) or for JDE, %char(mydate:*CYMD0). I can do things like mydate = mydate + %days(7). It's a snap. OK, you said please. I'll go away now.

Pete Hall
http://www.pbhall.us/



Steve Landess wrote:

Date field question...

There may be a few exceptions, but in JDE all date fields are generally defined 
as a 6-digit julian format - 105001, for example, indicates 1-January-2005.  
099001 indicates 1-January-1999.  (The '1' prefix indicates that the date is in 
the 21st century, a '0' prefix indicates 20th century).

Let's say you're defining a date/timestamp field (14,0 Zoned) -or- a date field (8,0 Zoned) in a non-JDE data base (DB2). Is our industry, is there a standard for populating these types of field? I have an idea as to how they should be populated, but would like another's opinion. 

Please do not confuse my question with the "date" data type that is now 
available.  I believe that the customer's requirement is to have this field defined as a 
numeric field...

Regards,

Steve





As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.