RE: ALL I/O in single module was(ARGH!!! (was file open with LR))

What subprocedures should make up this I/O module? One
getter/setter/validator subprocedure for each field in
the file? Are there any "best practices" examples of
this ILE RPG design pattern available on the web or in
publications? 

Should this separate I/O module be implemented as part
of a larger "data server" program that acts as the
"Model" in the MVC design pattern? 

Regards,
Jake




--- Booth Martin <Booth@xxxxxxxxxxxx> wrote:
> The benefit of having all validity checking in one
> place seems like a big
> win to me, especially when one begins to deal with
> data updates from places
> other than the green screen.


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree