• Subject: Re: Design shift of view
  • From: "James W. Kilgore" <qappdsn@xxxxxxx>
  • Date: Sat, 25 Jul 1998 08:42:48 -0700
  • Organization: Progressive Data Systems, Inc.

Robert Montague wrote:

> Hi
> Someone referenced the header/detail/footer concept and sort of linked
> it with MFCU's etc.   I think it is merely a logical result of an order.  I
> could
> go to a 1000 companies and their order and invoice printouts would be
> eminently similar, not because the programmer or management wants it
> that way--but perhaps the customer likes to see a detail invoice and the
> shipping company might need an address to ship to and the accounting
> department might like to receive the remittance at a certain address.

That was me.

It's the storage of information I was referring to, not the presentation.

You are correct in that this is the way the forms appear. (and always will)  The
question I rose was why should the underlying files look this way. I correlated
that we store disk data the same way we stored punched card data. Unit record

Although we can pick any length of record we want, we are still doing unit 
processing. Both logically within the program, and physically within the disk

The question then became, how can we logically do what we have always done, yet
change the underlying physical constraints of a "record" in order to permit
dynamic changes to a files structure while an application is in use.

James W. Kilgore

| 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

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].