|
This is one of the great reasons to go to QMQRYs. There is an interface similar to Query (but it also has ISNOT), but you can go to the SQL interface and use all its strength. > Yes, that works, but it gets messy when you have other criteria to test. > What's missing is the parenthesis. Without it, an OR can bite HARD on your > logic. > > 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 > > This example is very tame compared to some of the queries I've seen. > > Eric DeLong > Sally Beauty Company > MIS-Project Manager (BSG) > 940-898-7863 or ext. 1863 > > > > > -----Original Message----- > > From: Alan Novick [mailto:mida@pressmantoy.com] > > Sent: Thursday, July 25, 2002 8:13 AM > > To: midrange-l@midrange.com > > Subject: Re: negation of range > > > > > > I know I'm going to make a fool out of myself but I can't resist the > > question. Would this work? > > > > AND/OR Field Test Value (Field, Number, > > 'Characters', or > > ...) > > FIELD LT LowVal > > OR FIELD GT HighVal > > > > Alan Novick > > Pressman Toy Corporation > > New Brunswick, NJ >
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.