Ankur I've seen this before. The issue results from comparing a date/time field with a date field. I have workflow that takes the date field and sets a date/time field (display field).
Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <[email protected]> To: [email protected] <[email protected]> Sent: Wed Dec 13 07:25:37 2006 Subject: Date/Time in table field Qualification ** Hi Listers, I am trying a basic qualification in the Table field 'create_date'<=$Start_Date$ both the fields are the Date/Time fields of a regular forms. when I run it it gives "ARERR [313] Data types are not appropriate for relational operation" but when I try 'create_date'<=$DATE$ it works fine, in this one is date/time and other is date field. I am clueless as what needs to be substituted for 'create_date'<=$Start_Date$ to work. I know this topic has been discussed lot of times in past, have gone through the archives but couldn't resolve it. Ankur __20060125_______________________This posting was submitted with HTML in it___
