> > do you > think that the REPLACE ALL operation--because it is only locking the > entire file once versus each record lock inside the SCAN loop--would run > faster and be more desirable? Or would you prefer the SCAN loop with > the individual record lock to avoid the increased chance of contention?
REPLACE ALL is faster, more readable and more reliable... but impossible to use when you have many users updating the table. With the scan loop you have to make sure that you do not change a field that is part of the current index. Unless you suffer from performance issues, I'd use ALL/FOR. Christof _______________________________________________ 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.
