I wont go about it, last post I promise.  No-one is blaming previous devs.  Any software development has to have lifecycle management built in.  As new versions come up, new technology is implemented, there needs to be constant moitioring, refactoring, or even re-implementation.  So what was "The process is vast (hundreds of thousands of lines of code) and legacy - >25 years old" - may now, in the this year be reduced only a few thousand lines of code, which operates quicker, more robustly, and provide more functionality rather than less.  The only reason I point this out is because its the first thing I notice when joining a company is the vast mass of undocumented, mass of code from 25 years ago, which creaking and breaking, with patches etc. And users just hate using it.  Its all about cost now against benefit in the future, which admittedly is a hard sell.   With regards to the wrapper procedure, you can pop an idea into the ideas section.  Me, I personally think that would be an overhead (cost vs benefit again). ... View more