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



Hmmm.. Well, I added the WINDOW keyword to the message subfile control
record. "WINDOW(WINDOR)" WINDOR is the record format for the window that has
the positions in its WINDOW keyword.

I already had a SFLMSGRCD() keyword - but may have positioned it
incorrectly. I increased the size of the window by one to make sure I wasn't
bumping into the border.

Now I am blowing up...

Message ID . . . . . . : CPF500A Severity . . . . . . . :
40
Message type . . . . . : Sender
copy
Date sent . . . . . . : 04/14/08 Time sent . . . . . . :
14:33:36


Message . . . . : Window does not
exist.
Cause . . . . . : An attempt was made to display a window record in a
window
that is not currently being
displayed.
Recovery . . . : Either specify a record format name of a window that
is
currently being displayed, or specify a window position in the
WINDOW
keyword to create a new window. Then try the request
again.

But the window IS showing... ???

On Mon, Apr 14, 2008 at 2:18 PM, Lim Hock-Chai <
Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:

You'll need to add the WINDOW keyword on the record format of the Error
Message Subfile control. The parameter of the WINDOW keyword should be
the record format name of the window where you want the message to
appear. You should also use the SFLMSGRCD() keyword in the Error
Message subfile to indicate which line you want the message to appear.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.