• I'm going to read into that answer a little and say that I hear you already recognize some shortcomings. ROI on upgrades is a bit difficult to calculate, especially due to the differences between upgrading from say VB6 to VB2003 (very difficult) and VB2005 to VB2012 (easy). The pains experienced years ago tend to linger, despite any new data. Also, published estimates of upgrades have always been useless in my opinion, so it's more about developing trust between the team and management, which is a different topic.

    So, I'm really looking for strategies, other than resigning to it, but if others think the obvious answer is "just upgrade", then I'd be glad to hear that too.