This is sort of like the Proc Statement IF E = 401 working with the ERRMSG file.
----- Original Message ----- From: "Pingilley, Ron" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 11, 2004 10:48 AM Subject: RE: [U2] broken up SELECTS > The UV keyword REQUIRE.SELECT makes this a possibility. On the Mentor and Ultimate systems I cut my teeth on, if the 1st select returned zero records, then the second select would select against the entire file. Once I moved to UV, and learned about REQUIRE.SELECT, then breaking out SELECT statements made more sense. > > --Ron P. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Adrian Matthews > Sent: Thursday, November 11, 2004 9:27 AM > To: [EMAIL PROTECTED] > Subject: RE: [U2] broken up SELECTS > > > It's something I've always done over the last twenty years. The select > processor in theory should apply optimisiation but I always break my > statements down to reduce the working record set and to increase readability. > > Makes very little difference on smaller amount of records but makes a huge > difference when record counts get into the millions, especially on distributed > files or selects which work on a mixture of non-indexed and indexed fields. > ------- > u2-users mailing list > [EMAIL PROTECTED] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
