× 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: ERRMSG Problem
  • From: "Buzz Fenner" <bfenner@xxxxxxxxxxxxxxxx>
  • Date: Fri, 31 Mar 2000 16:20:49 -0600
  • Organization: City Water & Light

Hey All,
 
I posted this once and got only one response which did not resolve my problem, so I will try one more time.  I have a display file with a subfile.  The control record (SFCTL1) has several I/O fields with ERRMSG's tied to them.  The subfile (SFRCD1) has line items + prices.  Beneath SFRCD1 is a format (CMDKY1) that has one O only field (the total of the item prices) and F keys available to the user.  The records are displayed, input is edited.  The problem is, the ERRMSG keywords do not function as they should.  In fact, nothing happens.  CMDKY1 is aware of the errors because the F key for update does not toggle on.  If I comment-out the one O only field in the CMDKY1 format and run the program, the ERRMSG keywords work.  The code is very simple:
 
*in01            Doueq*ON
 
                    WriteCMDKY1
                    ExfmtSFLCTL
 
*in01            Ifne *ON
 
        Edit Input, etc.
 
Can anyone explain what is going on here and how can I force those ERRMSG's to work?  Keywords on SFLCT1 include OVERLAY & PUTOVR with OVRDTA's on the I/O fields.  The CMDKY1 format has no record-level keywords.
 
TIA
 
           

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.