CFLOCK has nothing to do with what you are needing. Assuming you are using a DB to store these 'tickets'...you could
1) add a field called INOUT, when a ticket is checked out, update inout to OUT. When the ticket is saved update inout to in. Now when someone tries to open a ticket in edit mode, check this field first. 2) a more relational way, perhaps, is to create a table say CHECKEDOUT that stores only checkout tickets. When a ticket is being edited, add the ticket number to this table, once saved remove it. If an edit is requested check this table, if the ticket id is in the table, open in read only mode. HTH Doug >-----Original Message----- >From: Clark, Aimee [mailto:aclark@;stinsonmoheck.com] >Sent: Friday, November 15, 2002 1:00 PM >To: CF-Talk >Subject: Locking pages in CF > > >I have an application in which techs can click to edit a ticket in the >ticketing application. I would like to know what the best way >is to prevent >Tech B from getting into a ticket that Tech A is already in >and currently >modifying. > >I am thinking of using cflock, but where do I put it? > >Thanks, > Aimee' Clark > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
