It's fine when they're properly presented as Ds and Ts in the DDS, but a
major pain when they're all represented with INT 8 for the dates and INT
4 for the time. :O

/b;

-----Original Message-----
From: Wilt, Charles [mailto:WiltC@xxxxxxxxxx]
Sent: Friday, October 19, 2007 2:42 PM
To: Midrange Systems Technical Discussion
Subject: RE: Converting Integer to Dates

Just a point of fact...

DDS handles date & time fields just fine.

Charles


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Friday, October 19, 2007 2:40 PM
To: Midrange Systems Technical Discussion
Subject: RE: Converting Integer to Dates

And that's the unfortunate state of affairs for 90% of the
programs we have here - they all use a DDS to create the PFs.

/b;

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Friday, October 19, 2007 2:26 PM
To: Midrange Systems Technical Discussion
Subject: RE: Converting Integer to Dates

You know, if the software companies would abandon DDS and
move to SQL's DDL to define their fields, and, use real date
fields instead of numerics or characters, that could not
possibly occur.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/19/2007 02:10 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Converting Integer to Dates






In SEQUEL, it's CVTDATE(yourdate,ymd1). Plus, it'll be invaluable in
finding
bogus dates your application software package stuffed into
your files.

I just found a case where an A/R aging routine made a bunch
of due dates
equal to 20070931 for customers whose terms code is thirty
days, and the
invoices were created on September 1st. This was following a package
upgrade
done in August. Don't software companies have people to test
their code
anymore? Sheesh.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
vhamberg@xxxxxxxxxxx
Sent: Friday, October 19, 2007 12:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: Converting Integer to Dates

Depends what you mean by easy!!

Something like a bunch of character casts and substrings is
what you do.

date(substr(char(yourdate), 1, 4) concat '-' concat
substr(char(yourdate),
5, 2) concat '-' concat substr(char(yourdate), 7, 2))

will get you the date in a date data type - similarly, do that with
yourtime

time(substr(char(yourtime), 1, 2) concat ':' concat
substr(char(yourtime),
3, 2) concat ':00')

Better yet, write a user-defined function that'll take the integer and
return the date - much cleaner - and RPG can do the
conversion much more
neatly.

HTH
Vern

-------------- Original message --------------
From: "Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx>

Hi All,



Is there an easy way in the SQL interpreter to convert an
integer to a

date? The original programmers thought it was cool to dump all
date/time fields into int 8/4 which sucks when you're trying to do
calculations on them (they also like to use a 25h clock,
but that's a
whole other can of worms).



I tried a cast([field] to date), but the interpreter didn't
like that.

I'd prefer to have the SQL server return the value without
having to
resort to additional code in my RPG program. As I
mentioned, the field

are set up as YYYYMMDD (8int) and times are set to HHMM
(4int - no SS
in

our tables!).



Thanks,



/b;



-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-



--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not
a named addressee you are hereby notified that you are not authorized to
read, print, retain, copy or disseminate this communication without the
consent of the sender and that doing so is prohibited and may be
unlawful. Please reply to the message immediately by informing the
sender that the message was misdirected. After replying, please delete
and otherwise erase it and any attachments from your computer system.
Your assistance in correcting this error is appreciated.


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].