Sorry guys, I just realized that the field on the source form is date/time field not date, so it was a false alarm. The bug is there, but it's in my mind. It's late friday...what can I say?
I just confirmed that arithmetic works ok in table qual if both fields are date. So what it basically means is that arithmetic is allowed in table field quals as long as both sides of the operator are date fields. Or both are date/time fields. When one side is Date/Time, and another one is Date, even without any arithmetic, it doesn't convert date to date/time or the other way around, as I would like it to and throws this error. On Set fields, such a conversion occurs so I still want to call it a bug, but this time I'm not sure it's in my head or out there in reality. I will think about that Monday. Again thanks Eric and Joe. ----- Original Message ---- From: Eric Cleereman (IT) <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, November 2, 2007 5:50:16 PM Subject: Re: Arithmetic on date field values...doesn't work in table qualification ** Hi Rabi, Have you tried performing the calculation on the left side of the qualification, such as: ( $Date Field On Current Form$ + 1 ) < 'Date Field on Source Form' Not positive that will help, but I've seen other qualifications in the past, where it worked fine with the arithmetic performed on the left, but not the right. Also, are you positive the date field on the current form has a value at the time the table qualification is read? In other words, it is not evaluating as: 'Date Field on Source Form' > ( $NULL$ + 1 ) Eric Cleereman -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Rabi Tripathi Sent: Friday, November 02, 2007 5:29 PM To: [email protected] Subject: Arithmetic on date field values...doesn't work in table qualification I can do arithmetic on a value on a date field fine to do stuff like add 1 to a date in set field action to get the next day. However, in a table's qualification, a clause such as: 'Date Field on Source Form' > ( $Date Field On Current Form$ + 1 ) or any other kind of addition to a date field on source or current form's date field causes: ARERR [313] Data types are not appropriate for relational operation on refreshing the table. Since arithmetic works in set field actions, there is not logical reason it shouldn't work in a table field qual, so I want to mark this as a bug. Anyone seen this? I don't think date/time fields have this issue. I am trying to avoid having to do the arithmetic on a separate field and reference that field in the qual. ARS 7.0.1 p3 on Win 2003. Remedy User 7.0.1 p4. TIA. __20060125_______________________This posting was submitted with HTML in it___ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __20060125_______________________This posting was submitted with HTML in it_____20060125_______________________This posting was submitted with HTML in it___ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
