|
-- -- [ Picked text/plain from multipart/alternative ] My personal favorite on this sort of thing is two queries, with the first query being output to a file that is in turn queried by the second query. Power Users pick up on this idea quickly and the selections are much easier and more accurate. Also the queries seem to run quicker. In this instance I might choose query 1 to select the customers, and records for year 2002. The second query would select the range of months, do any joins, and layout the results, breaks, etc. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: midrange-l@midrange.com Date: Thursday, July 25, 2002 09:43:02 To: midrange-l@midrange.com Subject: RE: negation of range > From: DeLong, Eric > > Consider > ID=1 AND YEAR=2002 and MONTH<=6 and (CUSTOMER<123 OR CUSTOMER>456) > which is not an uncommon type of query. With the weak nature of query > selection entry screen, you'd have to code it like > ID=1 AND YEAR=2002 and MONTH<=6 and CUSTOMER<123 OR > ID=1 AND YEAR=2002 and MONTH<=6 and CUSTOMER>456 Just a thought - what about creating a logical file with the selection criteria and using that as input to the query? Joe Pluta www.plutabrothers.com -- [ Content of type image/gif deleted ] --
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.