> > I've always done stuff like > > Sele MySharedTable > > Replace x with y > Replace z with a > Replace t with v > > Rather than doing it all in one Replace command. > > I started doing this from a troubleshooting point of view ... if one of the > fields had a problem with the replace... it was easy to find which one. > > Will this: > a) slow down the system as opposed to one replace command?
I've tested this in the past, and the all-at-once approach is faster. I presume it is because of record/file locking... each REPLACE command does a lock, the replace, then a release... rather than just locking/releasing once... at least that's my theory... -- Matt Jarvis Eugene, Oregon USA _______________________________________________ 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/capt54ra+qefgyvmbzsbdrcu+6ugnnrkvh6wjkzbr3lo-opw...@mail.gmail.com ** 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.
