× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Omit/select in a logical file's dds
  • From: boothm@xxxxxxx
  • Date: Sun, 14 Feb 1999 01:33:45 -0500

This has me talking to myself.

I have a simple physical file with 300 records and 8 fields. It is non-keyed.

There is a logical file over it with a non-unique key field of 6 digits.  I can 
chain to the file and find the records I want.  I can set lower limits and the 
file is set to the right place.  

But if I add in two Omit statements I can't get a successful chain, and setting 
lower limits sets the file at the lowest key in the file, not the lowest key 
that meets the criteria of the setll.  The Omit statements omit the record if 
two other fields do not compare to the values in the dds.

RUNQRY against the file selects correctly and orders the file correctly.

So why can't I get a successful chain when the Omit statements are in place?

-- 
-----------------------------------------------------------
boothm@ibm.net
Booth Martin
-----------------------------------------------------------

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.