Re: Database access as service pgm or bind by copy?

[Scott Klement <klemscot@xxxxxxxxxxxx>]

I would definitely make something like this a service program.  Even if
only one program is using this data, some day others will too.

One of the big advantages of doing it this way is that if you're careful
in the design of the service program, you won't need to recompile all the
programs when a field in the database is changed.


On Fri, 5 Jan 2001, Jade Richtsmeier wrote:

> A database 'server' program would provide access to a file (add, delete,
> update, retrieve).  For example, if you have a name and address file, any
> program that required the name and address to be displayed/modified/printed,
> it would call this database 'server' program to obtain the data and, if
> necessary, update the database. (One procedure would get the record from the
> database, and another procedure would write/update/delete the database
> record.)

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---