|
On Tue, 11 Mar 2003, Gary Guthrie wrote: > > It's more than somewhat true. It's absolutely true. Only the most recent > job-level overrides survive amongst programs when each of these programs > has its activation group attribute set to value *New. > I didn't want to completely scare him away. The solution is quite simple, just do your overrides in the same activation group. > > I don't understand how folks can come to such conclusions in such a > void. While it might be true that a considerable portion of your > applications may adhere to such a scheme, it's not wise to blindly > follow such a rule of thumb. Proper assignment of activation groups > requires thought - you need to survey your applications and application > goals and make your decisions based on specific needs rather than based > on some "rule of thumb" general scheme. This becomes increasingly true > when you integrate applications with each other. > That's what I always say as well, Gary. But, people then are unwilling to even try because they think they'll need to spend a lot of time learning things. You have to start somewhere, and grow gradually, otherwise you get overwhelmed.
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.