Hello Spencer,

Are you testing the code from Update Mode? If not the code will have no effect, since it references the Search/Update Menu. I copied your code and ran it in Update mode and it asks me if I am sure I want to delete the record when the code is ran.

When Delete Record (F3) is clicked on the menu tree, or run using @SelectTreeItem(), it checks to see which form had focus. In the case you just described, the Main form is going to have focus since the Command Button is on the Main Form. When you click the Command Button the Main form becomes the form with focus. So the current record in the Main form will be deleted when the button is clicked. If you put the command button on the Subform then the @SelectTreeItem() will delete the current record in the subform.

-Ray

Ray -

I think my brain must be "fried."   I saw your answers in the other thread but at this point, I feel so overwhelmed I am having trouble figuring out my own questions - let alone your answers.  lol

BUT, let me tell you what I tried and I don't understand the outcome.

Since I can't see a command box in table view, I added a text LE (Delete) to the subform itself.

I used the following code in the on-element-entry event of the Delete LE.

var vDelete as Int
vDelete = @SelectTreeItem("Search Update Menu!Record Commands!Delete Record (F3)")  

While viewing the main form with the sub-forms, in table view, in Search/Update mode, if I click on the Delete LE I am asked whether I want to remove the record (which is expected).  If I select "No" programming stops (also as should be expected).

If I select "Yes", however, the appropriate sub-form record is deleted (as expected); HOWEVER, I am then asked the same question over and over.  I think there are about 30 subforms in the database and that's about how many times I am asked the question ... so it seems that the selecttree command is executing for every record in the database. 

Now what am I overlooking?

Bob's solution is the safest solution. But, you might be able to add a ThrowFocus to another LE to prevent the repeated code execution.

Spencer,

Did adding a ThrowFocus work to stop the multiple code executions?

If not, maybe you could use a GlobalValue to flag when to recalculate. The following code should give you an idea of how to implement it.

[Code for On Entry to LE named Delete in the subform]
var vDelete as Int
GlobalValue("Recalculate", 1)
vDelete = @SelectTreeItem("Search Update Menu!Record Commands!Delete Record (F3)")
ThrowFocus(Track Title)

[Code for On Entry to LE named Track Title in the subform]
var vLoop as int
var vTime as time
var vCnt as int
if @GlobalValue("Recalculate") = 1
  {
  GlobalValue("Recalculate", 0)
  vCnt = @FormResultSetTotal("Track Details")
  vLoop = 1
  vTime = 0
  while vLoop <= vCnt
    {
    vTime = vTime + @ToTime( @FormFieldValue("Track Details", "Track Length", vLoop) )
    vLoop += 1
    }
  FormFieldValue("MyMainForm", "MyTimeLE", 0, vTime)
  }
 

I have not tested this, but it should be pretty close. It should allow you to click in the "Delete" LE in the subform, which will set the Recalculate flag, delete the current record, and send focus to Track Title. The Track Title code will see that the flag is set, which will reset the flag back to zero, loop through the subform records to total them up, and then post the total in the Time LE on the parent form.

I used what names I could figure out from the image you posted. The rest, you'll need to change to reflect the actual names.

I don't think we can put all of the code into one LE, because you would end up in an endless loop that would delete all of the records. (Well actually, I have an idea how to make it work that way, but it would be more trouble than it's worth.)

If you try this, let me know how you make out.

I had to move the @SelectTree command over to the Track Title LE like this:

[Code for On Entry to LE named Delete in the subform]
GlobalValue("Recalculate", 1)
ThrowFocus(Track Title)

[Code for On Entry to LE named Track Title in the subform]
var vDelete as Int
var vLoop as int
var vTime as time
var vCnt as int
if @GlobalValue("Recalculate") = 1
  {
  GlobalValue("Recalculate", 0)
  vDelete = @SelectTreeItem("Search Update Menu!Record Commands!Delete Record (F3)")
  vCnt = @FormResultSetTotal("Track Details")
  vLoop = 1
  vTime = 0
  while vLoop <= vCnt
    {
    vTime = vTime + @ToTime( @FormFieldValue("Track Details", "Track Length", vLoop) )
    vLoop += 1
    }
  FormFieldValue("MyMainForm", "MyTimeLE", 0, vTime)
  }
 

This works fine the first time you click on the "Delete" LE. But after that, ThrowFocus doesn't trigger the On Element Entry event. This may be a bug with Sesame - the fact that the On Element Entry & On Element Exit events are not executing when focus is moved with ThrowFocus. They do execute if focus is moved with a mouse-click. But, because the events are not working the way that the code expects it to, the GlobalValue may not get reset to zero. Then the code may execute when you click on the Track Title element in another record, deleting that other record.

So, if the On Element Entry event was triggered by the ThrowFocus command, the code above would work perfectly. But, since it is not, I have had to completely rearrainge things. This is the best I could come up with:

[Delete :: On Element Entry]
if @IsBlank(Delete)
  {
  Delete = "X"
  ThrowFocus(Track Title)
  }

[Track Details (YourSubformName?) :: On Element Exit]
var vDelete as Int
var vLoop as int
var vTime as time
var vCnt as int

if Delete = "X"
  {
  vCnt = @FormResultSetTotal("Track Details")
  vDelete = @SelectTreeItem("Search Update Menu!Record Commands!Delete Record (F3)")
  if vCnt = @FormResultSetTotal("Track Details") then Clear(Delete)
  vCnt = @FormResultSetTotal("Track Details")
  vLoop = 1
  vTime = 0
  while vLoop <= vCnt
    {
    vTime = vTime + @ToTime( @FormFieldValue("Track Details", "Track Length", vLoop) )
    vLoop += 1
    }
  FormFieldValue("MainForm", "MainFormTimeLE", 0, vTime)
  }
 

This works pretty well. The main drawback, is that you need to click in the Delete element, then click in any other subform element (or on another line in the subform). Which means it requires 2 clicks to get the warning message about deleting a record.

One caution: don't answer yes to the question if clicking in the parent form is what brought it up. That may delete the parent form. Other than those two things, it works quite well.

One thing that works better now, is that there will be an "X" on the record that you are being asked whether or not to delete - helping to clarify which line you clicked on. If you answer no to the question, the Delete element is cleared.