I'd argue that once you move up to more complex data especially from
more than one file you've gone beyond the simple "file encapsulation"
to the "business object encapsulation" Scott, myself and others
prefer. :)

Actually, when given the opportunity, I'll use both levels of
abstraction. I'd encapsulate file i/o in protected procedures (ie.
useable only from within the *SRVPGM) The publicly accessible
procedures would provide the business object/methods.

Even in those instances, my file i/o routines are often more than just
simple getters/setters; they provide a named function for example
InvMstr_ChangeLocation() updates the location field of the Inventory
Master file and is called by various Inventory_MoveXxxx() type


On Wed, Apr 4, 2012 at 5:55 PM, Rory Hewitt <rory.hewitt@xxxxxxxxx> wrote:
Although we haven't used it
in anger, there's also the possibility to return more complex data
(possibly from more than one file) depending on the version number

This thread ...


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

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