× 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.



From: David Williams

Why not take the 15 minutes to write the matching
record program that suits this situation rather than
spend several hours figuring out all the possible way
to make another less suited alternative work? If I
only had a dollar for each matching record program I
wrote on the System/3 I could be retired by now.

Yep. In this case, the entire program wouldn't be anything more than:

If not *INMR or
((filea.field1 <> fileb.field1) or
(filea.field2 <> fileb.field2));
Write PrintRec;
Endif;

You'd need input specs to define the record identifying indicator for each
file (say 01 and 02) and to specify the match condition. The program would
print one line for each record in only one file, and two lines for records
that are in both files both don't match. Use 01 and 02 on the output spec
to specify which file is being printed.

If you were a little creative in your D-specs, you could just compare two
data structures instead of individual fields.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.