× 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've used this for years, before date fields (I see no reason to make
them a date only to move them back into numbers)

d $FlipDate1 1 6s 0
d $FlipDate2 7 12s 0
d $ymd 5 10s 0
d $mdy 3 8s 0

c* ymd to mdy

c eval $FlipDate1 = Oldymd
c eval $FlipDate2 = Oldymd
c eval Newmdy = $mdy

c* mdy to ymd

c eval $FlipDate1 = Oldmdy
c eval $FlipDate2 = Oldmdy
c eval Newymd = $mdy



On 9/5/07, Pete Helgren <Pete@xxxxxxxxxx> wrote:
What would be the most expedient way to convert a 6.0 numeric field that
represents a date in MMDDYY format to a 6.0 numeric field that
represents a date in YYMMDD order? The resultant numeric is used in an
SQL statement comparing it to a numeric (not a date) field. The old
technique of YYMMDD = MMDDYY * 10000.0001 appears not to work because
the program is cranky at runtime about the result field not being large
enough.

Since the compare is a numeric I figured that the math would be
numeric. Or, is using a date field and converting it to a numeric host
variable for the SQL the way to go?

Pete Helgren

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.