× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Database access as service pgm or bind by copy?
  • From: "Jade Richtsmeier" <jade.richtsmeier@xxxxxxxxxxxxxx>
  • Date: Fri, 5 Jan 2001 14:24:54 -0600

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.)




----- Original Message -----
From: "Scott Klement" <klemscot@klements.com>
To: <RPG400-L@midrange.com>
Sent: Friday, January 05, 2001 1:39 PM
Subject: Re: Database access as service pgm or bind by copy?


>
> When you say "database server program" what are you referring to?  What
> will this module do?  What will need to call it?
>
>
> On Fri, 5 Jan 2001, Jade Richtsmeier wrote:
>
> > 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
> +---
>

+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.