RE: SQL date comparison - a better way?

["Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx>]

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.