On element entry programming, gives a total for line items.

I have to click the element, then go back to sub-form click the last element and then back to grand total element:

var a as int=1
var vmax as int = @formresultsettotal("Itemsused")
Var vgrandtotal as double = 0

while a <=vmax
{
vgrandtotal=vgrandtotal + @Tonumber(@formfieldvalue("Itemsused","Total",a))
a=a+1
}
Grand total0=vgrandtotal

???
Was working before I upgraded with no problems.

Quote:

Send it to me at Support@Lantica.com and I'll have a look at it.

-Ray

Unless I am looking at the wrong form the 'Itemsused' form is a Table View subform and not a Form view subform. I am on the Materials tab of the Closeout Form.  Is this the right place?

-Ray

Hello Robert,

Here is what is happening. The first click out of a Table view subform onto the main form is not firing the On Element Entry event for that element for some elements. If you click in another element on the main form and then into your Grand Total element the code runs fine. If you move your code from the On Element Entry event of the Grand Total0 element to the On Element Entry event of a button the code runs fine. You can click right on the button when you leave the subform and the code will run.

Next time be sure to include the Username and Password.

-Ray

Quote:
 
This raises all kinds of questions..

Is this by design?   ???

Has it always been this way, or new with 1.1.3?   ???

Which types of elements will not fire when getting focus from a table view subform?  ???

If there are certain elements that need this to fire properly, then shouldn't the programming be moved to OnFormEntry?  ???

And will they really fire there OnFormEntry when getting focus from the table view subform.?  ???

Putting into OnFormEntry would tend to slow down record advances/backscrolling for programming that might not otherwise need to run except OnElementEntry

===============================
This sounds unreliable to rely on someone to remember to click on a certain element when they leave the table view subform.  There is no way we can count on that always happening.   

This sounds like it does need to be corrected to fire immediately regardless of where the focus came from.  Or provide a function to use when focus changes between forms to use with IF and programming statements. 
Like:
If @FocusFromSameForm() do nothing
else
IF @FocusFromOtherForm() do something

Quote:
That is exactly the point I was trying to make.

I understand that this could be a bug vs. design.  But some strange things are by design, thus my question. 

Since this is a "new" bug, then I should stay with 1.1.2 until this is fixed?  If NO, then we need a list of the types of elements that will not fire properly so that we can modify programming as needed.