Number of rows in Detail Area (AP20.1)

In Design Studio - not that I know of.

Not really, It is defined by the COBOL program underneath.

You could create additional detail lines and write code with javascript behind the Design Studio to call AP20.1 an additional time for each additional 5 lines created but it is a little complicated, you would have to add additional code for both processing changes and inquiry.

Thanks Terry. Is there a method other than Design Studio? There apparently is quite a bit that must happen on the back end when a change like this is made, e.g.knowing the number of rows to read, etc.

Thanks Gary.  That's what I was afraid of.  It sounds like to COBOL program has an OCCURS clause (or something like it) that determines the number of rows.  Correct?

First, let me get on my soapbox.

You should not be customizing anything in the product, since doing so incurs what is referred to as "technical debt"...in other words, in addition to greatly increasing the cost of supporting your users, you will certainly pay a high price down the road with CTPs, MSPs, and upgrades, etc. (if you're new to Lawson, you'll have to trust me on this...)

Now, stepping off the soapbox, I will say that I have done this type of COBOL customization to support larger forms, and my experience is that it depends on the form. In some cases it's very easy, but in some cases it is quite difficult. I can tell you for a fact that I had to remove this exact customization from a client's customized AP20 when they went from v8 to v9, since some of the library code that is used by AP20 is hard-coded/limited to pass 5 detail lines back and forth to AP20. So, it was easier, and cheaper, for the client to just live with 5 lines per form than to have to maintain this customization.

Theoretically, you can write your own customization in Design Studio (or any other web front-end) that maintain internal arrays, etc. and interacts with the back-end form by always passing the values back to row 1 on the back-end form. But I wouldn't go anywhere near that sort of a customization.

It's just a limitation that the customer has to live with, having chosen Lawson. Hopefully someday, Lawson might even discover the vertical scroll bar!

John - I hope by when you say "customizing anything in the product" you're referring to changes to the underlying COBOL or RPG code, and NOT using Design Studio. There are many many changes you can make using just DS to enhance the funtionality of a form. It just so happens modfing the underlaying logic of the program is one you can't change.

Posted By Tom Sinkula on 11/16/2009 03:52 PM

Thanks Gary.  That's what I was afraid of.  It sounds like to COBOL program has an OCCURS clause (or something like it) that determines the number of rows.  Correct?

 

That is correct.  What is it that you are trying to accomplish that can't be done with the Page Down/Page Up?   If it is that you want them to be able to change all distribution lines with a single click of change?  You could "simulate" it but like I said, in the background you will have to call AP20 multiple times for each 5 lines and track which line is on top, (or call AP20 for each line puting it on the first line which is even more inefficent but is how Self Services handles detail lines). 

I would suggest if you want to go that route that you might consider writing an applicaiton in html or VB rather than DS,  This requires some knowledge of how to call AGS and DME.

Posted By Terry P. on 11/16/2009 04:09 PM
John - I hope by when you say "customizing anything in the product" you're referring to changes to the underlying COBOL or RPG code, and NOT using Design Studio.

Correct, COBOL or RPG. For the most part DS is OK, but there are some cases where upgrades, patches can break DS modifications. 

One interesting theorist angle to add to this discussion. One could argue that the only customizations that should ever be made to a "vended product" are ones being made to the "presentation layer";  the "5 lines per form" (which is just plain dumb) falls into that category.  However, changing it utlimately requires changes on the back-end form (i.e .the application layer).

John and Terry - Thank you for your responses.  We have had a user request this change and I'm trying to research it.  If the change means underlying COBOL or RPG changes, it's out of the question.  If it's simply a Design Studio change, then it may be reasonable--but it doesn't like this is the case.  Once again, thanks for your input.

Tom