|
We have a single copy member for all our service programs that holds prototypes and other definitions. We keep this member in a separate application in our change management system (Aldon) so when it's promoted we can tell Aldon not to select all its dependent objects for recompilation. If I recall correctly, you could do something similar in Turnover. Place all the copy members in their own library and make that library a separate application in Turnover. Would that help? Donald R. Fisher, III Project Manager Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@xxxxxxxxxxxxx <clip> One of the biggest practical problem I am finding with using one copy book per service program to store the procedure declaration is: Each time I add a new procedure to the service program, the copy book changes and as such I have to recompile all of my programs that use this. <clip>
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
