I'm finding code where the developer had done a SET ORDER TO and then SEEK command afterwards instead of using the SEEK(a,b,c) function with its parts. I'm not sure when the SEEK(a,b,c) function came to be, so perhaps this is because it was written prior to that?
IAC, I thought I had heard that doing a SET ORDER TO on a network table was slow or caused a performance hit, especially since all we want to do is use the index to check for the existence of a condition that could nowadays be done with the SEEK(a,b,c) function. While refactoring, should this be done (...replacing the old SET ORDER plus SEEK command with the SEEK function instead)? Just curious...tia! --Michael _______________________________________________ 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.
