I know you have got a few responses to this but just thought I'd add my thoughts to it..
You could run a direct sql to the database using an AL that sets the user login name in a character field when the record is opened on Window Open, only if the current value of that field is NULL. If the current value of the field is NULL on Window Open, set this field to the user name and if the $USER$ = this field allow update... Also on Window close if the $USER$ = this field, set that field to NULL. If the current value of the field is not NULL on Window Open, check to see if $USER$ = the field (as a user could possibly open another instance of the user tool). If the $USER$ does not match the value in the field, disallow updates. Not tried it but I don't see why it shouldn't work.. Cheers Joe ----- Original Message ---- From: Angelina B Mora <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, December 14, 2006 4:20:10 PM Subject: How do I create a "checking out" system ** Hello everyone! I was wondering if anyone has created a "checking out system" on Remedy tickets, to prevent 2 support techs from updating the same ticket at the same time? If so, can you please tell me how to do this? We are currently running Help Desk V. 5.0 and AR System Server 6.01. Thanks for your help!! Angie Mora Idaho National Laboratory 208 526-3535 [EMAIL PROTECTED] __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 ARSlist:"Where the Answers Are"
