I think it's best practice to type your variables outside of the loop Set var vBreak int While ... vBreak = 0
You could also try using "Goto" with labels in place of "While" to see if your problem is related to the While loop. Ben On Wed, Oct 31, 2012 at 11:40 AM, jan johansen <[email protected]>wrote: > Group, > > There was a discussion a few weeks back about WHILE loops. > > I have a routine that "partially broke" a few 9.1 updates ago. > I figure it is some sort of memory blow up. > > Here is the code > > WHILE vWODataRow <= .vCountBothRows THEN > SET VAR vBreak INT = 0 > EDIT USING WorkOrderDataRow WHERE WorkOrderTID = .vWODataRow + > CAPTION ' Incoming Data Entry ' > IF vBreak <> 0 THEN > BREAK > ENDIF > SET VAR vWODataRow = (.vWODataRow +1) > PROPERTY Measurements REFRESHLIST 'TRUE' > ENDWHILE > > Most of the time this works fine because the while loop is under 50 > itterations. > But if there are 200 itterations to go through, the system will lock up. > > Any ideas? > > This is the reason I'm playing around with a DB-Grid. I rarely use this > tool so > am a bit unfamiliar. > > Jan >
