RE: SQL date comparison - a better way?

Have you tried adding spaces to fill it up?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/14/2003 03:55 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "'Midrange Systems Technical Discussion'" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: SQL date comparison - a better way?


Rob,

How did you resolve the constants issue?  I think that's what is getting 
me.
I finally got it to work with a definition of 1 parm dec(8,0).

What I really want is cvtdte (dec(8,0), char(5), char(5))....  That way I
can call it like this cvtdte(fieldname, '*MDY', '*ISO').  When I add the
second and third parms I get the not found message again.

Rick

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Thursday, August 14, 2003 1:50 PM
To: Midrange Systems Technical Discussion
Subject: RE: SQL date comparison - a better way?

Exact parameter matching is important, and not just the number of
parameters.  I always had a bear of a time trying to use these by passing
in constants.  You know, like
Select filename.fld1, MyUdf('A',filename.fld2) from mylib/myfile filename

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin

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