×
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.
I'm not understanding why you need an H-spec to specify DATEFMT(*MDY)?
Can you make the global (H-spec) date format be *USA or *ISO and use
*MDY just for a specific field on the D-spec? Seems like this should
work...
Personally, it's always been my policy to use a format with a 4-digit
year on all calculations, database operations, etc. Especially since
learning our lessions with Y2K, it really doesn't make sense to use a
format with a 2-digit year.
The only place I'll use a 2-digit year is for displaying to a user (who,
in most cases, doesn't have any problems understanding which century the
date is from.) So I pretty much use *ISO everywhere except for the
last step of the process where the user sees it, where I convert it.
On 4/16/2014 1:05 PM, Horn, Jim wrote:
I have a file that contains a date field with a value of 9999-12-31. I
need to "chain" this record into a program that has an Hspec of
datefmt(*mdy). I am getting error RNQ0114, Date or timestamp value not in
correct range. If I change the program to datefmt(*usa) the chain works.
The program specs say I need to use datefmt(*MDY). Tried entering a D
spec with the field name with DATEFMT(*mdy). Didn't work. Any ideas?
Jim
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.
midrange.com
