Chas, the bad news you mention about paying for customizations to be re-done at every upgrade is unfortunately the case for just about any major customization. This is one reason that we finally dropped the major customization that we had in our database with the last upgrade we did. It was causing us to have to spend several thousand dollars every time we upgraded. It can potentially become a very big discincentive to staying current. Fortunately for us though, we had a recent change in one of our business processes that made the customization unnecessary. I now view major customizations as an absolute last resort, primarily because having them can put you in a situation in which upgrading becomes very expensive, making it difficult to stay current and take advantage of the fixes and enhancements of newer versions. I for one am very glad to be rid of our expensive customization. Now when there are fixes or enhancements in the native product that we need, we can upgrade to take advantage of them without paying out the wazoo. 
