June 21, 2007, 02:24 PM
John_EdwardsFaster Load Time in Maintain
Years back I used Maintain and the For-All-Next command so that it would only draw the four columns of the table that I was interested in displaying (out of about 200 columns) and it was FAR faster loading for obvious reasons.
I am in a similar situation now, but do not have my source code from 1999 to refer to. Question -- how do I infer/compute and For-All-Next so that it only brings down the few columns of data that I am interested in displaying? I have a grid that is loading too slow.
J.
June 21, 2007, 02:56 PM
Alan BMaintain always brings back data at a segment level, and as far as I know always has, with a for all next.
However calling (EXEC) a TABLE request, you can bring as many or as few rows as you want.
June 21, 2007, 03:03 PM
John_EdwardsThank you! That may have been how we did it.
J.
June 28, 2007, 11:44 AM
John_EdwardsA quick update for those finding this in a search, the EXEC call did not seem to load any faster. It appears the for-all-next logic has been optimized since I last used Maintain.
June 28, 2007, 11:50 AM
Francis MarianiShouldn't you be out campaigning or something?
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
June 28, 2007, 12:36 PM
John_EdwardsThere's two Americas. And I code Maintain for both of them.
JE