One long-standing trick to suppress the 1203 on a per-transaction basis is to use direct SQL to back up the Modified Date to the time the record was loaded into the client.
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Robert Molenda Sent: Thursday, May 17, 2007 11:14 AM To: [email protected] Subject: Re: Suppressing ARWARN 1203 Message Are you really-really sure you want to suppress the whole error message for EVERYONE on the server? The message is: This record has been updated by another user since you retrieved it. Which means that if you disable this message, you are disabling this checking for everyone. Probably not wise, because of multiple edits in incident/change will not be notified to the user! The question is, how are you doing the push-field? It sounds like some workflow might be updating (like via a cascade) back to your form. Thanks-n-advance; HDT Platform Incident / Problem Manager & Architect Robert Molenda IT OS PA Tel: +1 408 503 2701 Fax: +1 408 503 2912 Mobile: +1 408 472 8097 [EMAIL PROTECTED] Quality begins with your actions. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Oyefeso, Bola Sent: Tuesday, May 15, 2007 12:38 PM To: [email protected] Subject: Suppressing ARWARN 1203 Message I am pushing data from one field to the other and I am receiving this error. Does anyony know how to suppress this error message? Bola Oyefeso __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
