RE: negation of range

Sure, that's better than most of the solutions I've seen.  Still, for a $$$$
product, you'd think Query/400 would have a better interface.  We've lived
with this deficiency since Query/36.  :(

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



> -----Original Message-----
> From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
> Sent: Thursday, July 25, 2002 8:55 AM
> 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
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>