Then you could do it directly at DB level.. At the application level I would think you will get a response that it is working as designed as a date field is not an integer or a real field.. Its an integer field at the DB level.. Run a Direct SQL to update the value and that should do it for you. That will not require the addition of temporary field and hence is not really a workaround but a direct way of achieving what you want to..
Besides I do not really see what would be the problem using a workaround in this case. The process will be pretty much transparent to end users and there will be no additional or at least a significant cost to the database or the whole operation. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Rabi Tripathi Sent: Friday, November 02, 2007 5:44 PM To: [email protected] Subject: Re: Arithmetic on date field values...doesn't work in table qualification ** Thanks Joe, but as I stated such a workaround is what I am hoping to avoid here, because it's pretty lame that it should blame me for the calculation, because in another context it lets it thru. ----- Original Message ---- From: Joe D'Souza <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, November 2, 2007 5:36:24 PM Subject: Re: Arithmetic on date field values...doesn't work in table qualification ** Rabi, A workaround I can think up is as follows... 1) Try setting the value of the date field to a hidden temporary integer field using a Set Field action. 2) Add that integer field by 1 using another Set Field action. 3) Set that calculated value of that integer field to the date field using yet another Set Field action. I've not tried it myself, but I'm pretty sure that should work.. Cheers Joe D'Souza -----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. No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.15.19/1105 - Release Date: 11/2/2007 11:04 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
