|
Simon wrote: "...You could also write a new function in your service program -- reloadXrefCache() -- which causes the service program to reload its cache thus avoiding any nasty issues with activation groups. You will probably find this path much more flexible and useful in the long run..." Buck wrote: "...I would write a new function that refreshes the cache rather than kill two activation groups..." Scott wrote: "...I would echo what others are saying about having a reinitialize procedure in the service program..." Simon again wrote: "...regard this as a cartographers warning (i.e., Here be dragons!)..." ----------- This feels like an intervention... everyone gathered around firmly urging me to reload the data and not reclaim the activation group... My name is Jerry, and I'm a recovering RPGII cycle programmer. OK, OK. I'll write the reloadXrefCache procedure and skip the reclaim activation group... but I'm getting a latte afterwards. Thanks for the advice. Regards, Jerry Better living through fine code and hot coffee! -- -- -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup "Free price comparison tool gives you the best prices and cash back!" http://www.bestbuyfinder.com/download.htm
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
