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

Since our database I/O modules are used by many programs, we went with the
service program approach.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000



-----Original Message-----
From: Jade Richtsmeier [mailto:jade.richtsmeier@mcis.cog.mn.us]
Sent: Friday, January 05, 2001 10:30 AM
To: RPG400-L@midrange.com
Subject: Database access as service pgm or bind by copy?


We're trying to decide what is the best route to go with our database
'server' programs.  Do we create them as a service program or do we bind
them by copy to each program that uses them.  
 
We've read many places that service programs should be used for common
utilities and routines that many programs or applications use.  Bind by copy
should be reserved for modules that perform lower-level routines within a
larger program but are not shared among many programs or applications.
Okay, that said, what category does a database 'server' program fall into.
My guess is that the answer will be.......'it depends'.  
 
Any suggestion or comments would be very welcome!
 
TIA
+---
| 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
+---