I am trying to use formrunprogram("invoice","calc",PROGRAM_EVENT_LE_ENTER) on event exit of a subform element to run a calc button on event enter programming. (I do have #include "sbasic_include.sbas")

Basically I have a line items subform on an Invoice form. When the user exits the qty element I want the line to total but I also wanted the entire invoice to update the totals. I have a command button named Calc with a label of Calc Inv on the invoice form that when pressed runs a SubRoutine CalculateInv().  I was thinking that the formrunprogram( ) command would do the same as the user pressing the Calc button.

Am I not using this command correctly?

This is the on exit logic I am using.

//This Code calculates the total cost of the line item

Var vQty as Int

vQty = @TN(Qty)

If vQty > 0 Then
{
     Total = @TM(vQty * Price)
     ReadOnly(Total, 1)
formrunprogram("invoice","calc",PROGRAM_EVENT_LE_ENTER)
}


Issue2

While I am on subform questions I am trying to get the cursor to the first element in the line item element line on the subform . When I add an additional line to the line item subform either with F10 or
//new record
var nc as int
nc = @FormNewRecord("lineitems")

the cursor goes to the line above or the entire column (top to bottom) becomes highlighted. I have tried this
//new record
var nc as int

nc = @FormNewRecord("lineitems")

FormThrowFocus("lineitems", "prodid")

But it does not help. Do you all have any thoughts what I am doing incorrectly?

Thanks

Carl,

Thanks for the input.  The problem is with FormRunProgram( ) and Sbasic attached to a command button element. The FormRunProgram() works fine when the code is attached to a regular element. I ran into this back in August. (I found my same post in a search. At least I am consistent.)

Carl, thats good to know that it works for you even with a command button. It must be something I am doing wrong then. I will keep working on it.

Sesame is such a great product and lets me do so much while I know so little, its frustrating when I get in my own way.

Thanks for the help, it is always greatly appreciated.

Robert

Using the ENTER event of a button is not working because buttons do not actually run their code when entered, like a text box would. This prevents a button from running code just because you tabbed through it. Therefore, when FormRunProgram() sends the ENTER event to the button, it shrugs and says it's not meant to do anything.

We tell the click on a button to run the code residing in the On Entry event under the hood.

If one of you goes ahead and writes this up, we'll decide what to do about it. At the least, we need to document this.