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



Thanks for the explanation, Simon.  I've never had it explained in such
detail before.  I've always separated my header and footer when using
subfiles because my first attempt at a subfile lo these many years ago
failed to display the last couple lines of the record.  Now I know why it
didn't.

Trouble is, I have a program on another system that does exactly what I'm
attempting here, except the screens behave as I expect on the other system.
Both systems are at V4R1 and I checked the DDS keywords and compile options
used for each display file.

In any event, I have WINDOW specified on the formats I'm attempting to
display over the first format.  I also followed your suggestion about CLRL
with no success.  I attempted to use CLRL(*NO) and CLRL(11) (the number of
lines occupied by my window).  CLRL is apparently not allowed with SFLCTL so
I tried it on my footer record and on the first format.

I am beginning to suspect there are PTF differences between the two systems
or I am going senile.

Donald R. Fisher, III
Project Manager
The Roomstore Furniture Company
(804) 784-7600 ext. 2124
DFisher@roomstoreeast.com

<clip>
And there's the problem!  You said "the first format occupies all lines".
OVERLAY cannot be used on its own to put one record format over another if
they share lines on the display.  You must either use CLRL or separate the
formats.
<clip>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.