<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Thank you vey much Bob.<BR>
I tried moving the call to pre-update but lost the ability to have all the data commit together. I think your tip on setting the subscreen on line 25 may bear fruit!<BR>
One other thing - could you give me an example of how to use the restore=lines? quick procloc=xxx/xx restore=lines auto=xx.qkg??<BR>
<BR>
Appreciate all you do for us...<BR>
<BR>
Karen<BR> <BR>
> To: kbarrett00@hotmail.com<BR>> CC: powerh-l@lists.sowder.com; powerh-l-bounces+bob.deskin=ca.ibm.com@lists.sowder.com<BR>> Subject: Re: Screen display problem on return<BR>> From: Bob.Deskin@ca.ibm.com<BR>> Date: Thu, 10 Feb 2011 10:02:56 -0500<BR>> <BR>> I missed the very start of this, but I did see your last message. I have a <BR>> few things to add:<BR>> <BR>> First off, be very careful calling subscreens from the UPDATE procedure. <BR>> You want to make sure that your transaction and associated commit spans <BR>> the two levels properly. If it can be done as a separate transaction, then <BR>> call the subscreen in the PREUPDATE. However, that is unrelated to the <BR>> screen refresh issue.<BR>> <BR>> It is probable that the problem is because QUICK does not want to display <BR>> screens during the UPDATE procedure because unwanted things can happen. <BR>> Maybe not for relational, but for non-relational files.<BR>> <BR>> Here are some options:<BR>> <BR>> Try the RESTORE=LINES program parameter along with CLEAR ALL on the RUN <BR>> SCREEN. The RESTORE=LINES was introduced when we allowed subscreens to <BR>> overlay other screens in less than a 24x80 area.<BR>> <BR>> And if that doesn't work, you may be able to force things by using <BR>> application lines. QUICK has 240 application lines, basically its internal <BR>> screen memory. Most people don't bother with it any more because it <BR>> started out when using HP terminals which had more than 24 lines of <BR>> memory.<BR>> <BR>> By default, a screen starts ON LINE 1 FOR 23 LINES MESSAGE ON LINE 24. So <BR>> on the subscreen, try ON LINE 25. It will automatically take 23 lines with <BR>> the message line 1 after.<BR>> <BR>> Now when you clear and refresh, QUICK doesn't have to reload the screen <BR>> image. It has both in memory and hopefully will simply redisplay the upper <BR>> level screen.<BR>> <BR>> At least that's the theory.<BR>> <BR>> Bob<BR>> <BR>> <BR>> <BR>> From: Karen Barrett <kbarrett00@hotmail.com><BR>> To: PowerhouseList Post <powerh-l@lists.sowder.com><BR>> Date: 2011-02-09 07:40 PM<BR>> Subject: Screen display problem on return<BR>> Sent by: powerh-l-bounces+bob.deskin=ca.ibm.com@lists.sowder.com<BR>> <BR>> <BR>> <BR>> <BR>> Hi All,<BR>> <BR>> I tried these tips from Daniel but moving the call of the 2nd screen from <BR>> update to preupdate made no change and I had too much going on to treat it <BR>> as a slave.<BR>> Strangely, the choice of U, US, UR, and UN does! If U, all is hunky-dory. <BR>> Last time I checked, there was no way within the screen to <BR>> identify/control which update action the user chooses. Still, it is just a <BR>> display issue and if they forget to U, the funky look will remind them :-)<BR>> <BR>> Thanks and have a happy,<BR>> <BR>> Karen Barrett<BR>> <BR>> ;----------------------------------<BR>> <BR>> The second screen is called in the update procedure? If so, you should try <BR>> to call it in the preupdate.<BR>> <BR>> If this doesn't solve the problem, I would try to convert screen 2 into a <BR>> slave screen, receiving the primary file of screen 1 as master.<BR>> <BR>> Daniel Rodríguez-- <BR>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =<BR>> Mailing list: powerh-l@lists.sowder.com<BR>> Subscribe: 'subscribe' in message body to <BR>> powerh-l-request@lists.sowder.com<BR>> Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to <BR>> powerh-l-request@lists.sowder.com<BR>> http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> This list is closed, thus to post to the list you must be a subscriber.<BR>> Add 'site:lists.sowder.com powerh-l' to your search terms to search the <BR>> list archive at Google.<BR>> <BR> </body>
</html>