Eurico Chagas Filho wrote: > Hi > > Something odd just happened... > REPLACE Something WITH Newthing IN SomeTable > ---- > BEGIN TRANSACTION > --- > lSave = TABLEUPDATE(0,.T.,[SomeTable]) > ---- > ---- > It will fail, saying that a lock could not be placed, but only > sometimes. If I put the REPLACE inside the TRANSACTION it > works ok. >
Why use the 0 parm as the first parm in the TABLEUPDATE command...since you're wrapping it in a transaction, why not use 1 or 2? -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ 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.
