|
Rick, I have not found any official documentation, but then I also did not look very hard. The SQL Reference is a bit confounding when looking for something specific but you are not certain how it might be written in the book. I have many TESTSQL* members that I do tests on to see what happens. This is how I found out about this particular issue. This is the second time it was brought up. See archive thread starting: http://archive.midrange.com/rpg400-l/200507/msg00806.html Thank you, Matt Tyler WinCo Foods, LLC mattt@xxxxxxxxxxxxxx -----Original Message----- From: rpg400-l-bounces+mattt=wincofoods.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+mattt=wincofoods.com@xxxxxxxxxxxx] On Behalf Of Rick.Chevalier@xxxxxxxxxxxxxxx Sent: Friday, January 06, 2006 3:27 PM To: rpg400-l@xxxxxxxxxxxx Subject: RE: Date data type with embedded SQL Matt, That did the trick. Is this behavior documented somewhere? I never would have guessed to use like on the date and time fields. Here's what I ended up with. // Data Structure for returning Application information from SQL d RtnDtaSet ds Occurs(1280) Based(RtnDtaSet@) d AWrkQ 3a d ASysId 1a d ATrans 7a d AUser 10a d ALdDate Like(ixTDat) d ALdTime Like(ixTTim) d AAppl# 12s 0 d ADlr# 5s 0 d ALName 30a d AUpdt 1a d AApnd 1a d AHowR 3a d AGfxId 8s 0 d ABrnch 3s 0 Thanks, Rick -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tyler, Matt Sent: Friday, January 06, 2006 3:40 PM To: RPG programming on the AS400 / iSeries Subject: RE: Date data type with embedded SQL Rick, that is close. You cannot define a MODS with explicit date field definitions and use FETCH ... FOR x ROWS INTO ... The compiler only allows you to use LIKE() for date fields in MODS (at least on V5.2). The sample code I sent I can get it to fail if I reference REC1 with an explicit date field definition. Put the date, time definitions in stand alone fields and then use them as definition references in the MODS. Thank you, Matt Tyler WinCo Foods, LLC mattt@xxxxxxxxxxxxxx Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
As an Amazon Associate we earn from qualifying purchases.
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.