I see that growing to be too large to try to maintain. Too hard to search/edit/organize binding directories.
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
From: Scott Klement [mailto:firstname.lastname@example.org]
Sent: Friday, January 12, 2001 12:13 PM
To: Midrange-L (E-mail)
Subject: Re: Binding Directories
I'm confused. Why don't you just create a single binding directory that
contains all the service programs and modules listed in all the other
The binding directory is only used at bind time to determine which service
programs to search for procedures in. Simply adding all the service
programs to a single binding directory would have the same result as a
"binding directory of binding directories"
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.