I made this change to an app when I started here 2 years ago - the speed increase was tremendous. they apparently never heard of an IN clause, as they were still changing work areas manually using "select 1" before issuing a string of replace statements.
Those weren't the only changes I made to that system, but by far they were the most noticeable by the users. I have a file of 'interesting' code snippets from the previous programmers' code. My favorite was when they did a replace of a fixed-length string field with an rtrim() of itself for the entire 25000 record table - and they locked the table before doing so, but forgot to release it... ls -----Original Message----- From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On Behalf Of Christof Wollenhaupt I've seen a bunch of older code that uses a series of REPLACE commands: REPLACE field WITH value REPLACE field WITH value instead of a single REPLACE. Every line requires a new record lock. Consolidating those might help. ... _______________________________________________ Post Messages to: ProFox@leafe.com 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/0bac2c1927422843b2c121c8b41684af1e9f1...@dfw1mbx24.mex07a.mlsrvr.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.
