× 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: Getting the field attributes of a subfile record
  • From: Buck Calabro/commsoft<mcalabro@xxxxxxxxxxxx>
  • Date: Mon, 8 Feb 1999 08:38:55 -0500

On 02/06/99 10:29:10 PM Bob Larkin  wrote:

>OK everybody, please don't shoot, but I think we need to look at this a 
>different way.
>(Disclaimer - Worked 60 hrs this week, plus selling a house, and house 
hunting,
>so maybe my brain is mush.)

>Problem.
>      Record is in error, or RI would not be on in the first place. So if 
the
>record is in error,
>      it should be read and re-validated every time the subfile is 
processed. If
>on the other hand,
>      the RI is indicating a non-error condition, then the record should 
not be
>read unless it is
>      changed.

This isn't always the case.  Take the example of highlighting a line as an 
eye-catcher, like an invoice with an item having a large quantity.  This 
may not be an error, but we want to draw the user's attention to it.

>Solution.
>       Use the SFLNXTCHG keyword., and use READC to only read the subfile 
>records
>that have
>       changed. If a record fails validation, you can specify SFLNXTCHG on 
the
>record, which
>       will cause the record to appear to be changed, even if the user did 
not
>modify it.

This makes a lot of sense, but sometimes it's easier to spin through all 
the subfile records than it is to read only the changed ones.  Let's say 
you're trying to total up a list of debits and credits and want them to 
balance, or perhaps you have some special requirements for an invoice 
whereby you can't mix electronic and agricultural items on the same order 
due to cost centre restrictions.  Finally, a record can be valid when the 
transaction begins, but become invalid before the transaction is complete. 
Take the example of an item selling out of stock before THIS invoice is 
completed.  None of these objections are impossible to overcome, but it can 
get uglier with SFLNXTCHG.

otoh, SFLNXTCHG offers better program response if using a big subfile 
(imagine reading 2000 records rather than the one that changed)

Buck Calabro
CommSoft, Albany, NY
mailto:mcalabro@commsoft.net
+---
| 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-Ups:

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.