There seems to be a problem with totaling up a group of subform values!  (Version 1.0.2)

Here is a sample of the code I am using.

var vCnt As Int
var vLoop As Int
var vNetGain as double

vCnt = @FormResultSetTotal("Transactions Form")
vLoop = 1

while vLoop <= vCnt
 {
 vNetGain = vNetGain + @ToMoney( @FormFieldValue("Transactions Form", "Amount", vLoop) )
 // writeln("vLoop= " + vloop + "	vNetGain= " + vnetgain)
 vLoop += 1
 }

@msg("Net Gain = $" + vNetGain) 

This is set to activate at MainForm :: OnElementEntry.  After testing, I'm pretty certain the problem is that the @FormFieldValue() function is only able to retrieve the value of the first subrecord in time to be used in the loop.

So what happens is the @FormFieldValue gets the first subform's value, then since it's NOT being updated with the rest of them, the loop just keeps calculating with that first value (essentially multiplying it by the number of subrecords).

The reason I think the function is not getting the values in time, is that if you click on another element to re-trigger the code, it produces the correct total.  And by that time, all the subrecords have already been retrieved.  So this indicates that the code is not flawed.

Lanticans, can you let me know what your experience is with this?

Carl,

When your code runs, what is the value of vCnt?

Carl,

You've uncovered a fairly complex timing issue having to do with table view subforms. We've made an adjustment for 1.0.3 that should take care of it.

For now, you'll need to move your code so it's not trying to run immediately when the Form is opened. You can put it in an OnElementExit event, so it updates as soon as you press Tab or Enter. You can put it on a button that User can click to update the calculated values. Etc.

I hate to throw gasoline on the fire, but when the code listed in the 1st post above is combined with this next piece of code, it causes Sesame to crash!

It crashes when advancing to a new/blank form in update mode.  It appears that it crashes after backing up and displaying the previous record (the last one in the result set).

Located in [Form] :: On Form Entry

If @Update and System ID = ""
 {
 @Msg("No more records. Press Esc to exit or F9 for previous form.")
 ResultSetCurrentPosition(@ResultSetCurrentPosition() - 1)
 }
 

Again, this only happens when BOTH of these codes are in programming.  Individually, the don't cause any problems.

I can deal with not using these together, but do you think this may also be related the same timing issue?

Erika,

I have sent the app to support@lantica.com at your attention in the subject line.