RE: SQL date comparison - a better way?

[rob@xxxxxxxxx]

Thanks for sharing your results.  I'll have to remember that.

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/15/2003 07:56 AM
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?


Padding the constants with blanks didn't work but defining them as 
character
worked.  Thanks.

Rick


-----Original Message-----
From: Kevin Mohondro [mailto:kevin.mohondro@xxxxxxxxxxxxxxx]
Sent: Thursday, August 14, 2003 4:31 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL date comparison - a better way?

We ran into the same issues here with a couple of UDFs. Try using the 
CHAR()
function in SQL to specify your character fields. Like this:

cvtdte(fieldname, char('*MDY ', 5), char('*ISO ',5))

I believe it has to do with the fact that SQL sees the charcter values
you're passing as variable length fields and your UDF is expecting Char(5)
fields. But, that's just a guess on my part :).

-Kevin
Kevin R Mohondro
Programmer/Analyst
Ashworth, Inc.


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