× 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: RE: ERRMSG Problem
  • From: "Fisher, Don" <DRF@xxxxxxxxxxxxxxxx>
  • Date: Mon, 3 Apr 2000 07:48:27 -0400

When coding subfiles, I normally place SFLMSG keywords into the control
record and use the same indicators to condition DSPATR(RI PC) on the field
or fields in error.  This has yet to cause me a problem.
 

Donald R. Fisher, III 
Project Manager 
Heilig-Meyers Furniture Company 
(804) 784-7500 ext. 2124 
Don.Fisher@HeiligMeyers.com <mailto:Don.Fisher@HeiligMeyers.com>  

<clip>
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.   <clip>
 
+---
| 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 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.