Hi Dave Thanks for this. It's a simple system. I like it and it works Sytze
On Mon, Mar 10, 2008 at 8:30 PM, Dave Crozier <[EMAIL PROTECTED]> wrote: > Sytze, > Try an Flock() before you do the Replace all. This will let you see if > anyone else has a single lock on any record as it will return .F.. If the > result is .T. then you can go ahead with the replace all. > > Dave Crozier > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Sytze de Boer > Sent: 10 March 2008 02:05 > To: [email protected] > Subject: Record locking > > Hi Folk > > Scenario: > ONE user is editing a stock record in a form, and goes to lunch > ANOTHER user is doing something else and his module issues a command like > REPLACE ALL something > It hits the 1st user stock item who has a record lock on the item that's > being edited > > How do you guys overcome this kind of issue ? > > -- > Regards > Sytze de Boer > Kiss Systems > Ph: 64-7-8391670 > Mob:021 937611 > http://kiss.systems.googlepages.com > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
