Re: Separate buisness and display logic question

I have never had a problem understanding data being passed in the LDA.
It's no different than global variables, except it spans across
programs.

Would it have been easier if you had to change 20-30 parms that were
being passed as parameters?

Instead of simply an /include you should have taken the opportunity to
externailize the layout of the LDA so it would be standard and future
changes would be even easier.

Just because you are not comfortable with a technology doesn't mean it
isn't useful.

Albert

On Thu, Feb 3, 2011 at 10:32 AM, Harman, Roger <Roger.Harman@xxxxxxxxxx> wrote:

It's way too obscure using the LDA.  If I call a program with parm('mypo#'  'mychangeorder')  or look at the called program and see a plist or procedure prototype or interface, it's abundantly clear where the info came from.  If it is passed in the LDA, it's not at all clear how/where it came from or got there.

I recently had to change a number of programs that passed 20-30 parms in the LDA.  We were expanding an account number.   What a pain.  I did externalize the LDA layout to a '/include' but still far too much work.  Plus, the intermediate CL's that manipulated the LDA.