RE: Full free form and /copy or /include

This is exactly the case with our ERP system. I hated those subroutines so much that I created my own service programs to do the same thing (with SQL access)... I only use that in my code (not theirs).

But what are you supposed to do when you've invested money and many years into building your business (including other applications) on top of an ERP like this?
We started a UI modernization project that has failed miserably - I won't mention any names (yet). Then I think, should I really modernize the UI of something that has 1990's code under the covers?

What a dilemma.


<start soapbox>

They call it "technical debt" when you don't code it like you should the
first time, but guaranteed an old shop with lots of old code has a
subroutine copied all over the place that can be consolidated into one
or two procedures. Lots of places with 50 lines of code that could go
into one SQL statement.

</end soapbox>