Hello Spencer,

Quote:


Why loop through the subform to count the number of records when there is an SBasic Command @FormResultSetTotal() that returns the number of records in the subform.

-Ray

Ray -

The @FormResultSetTotal() command may come in handy for something else I want to do (or perhaps I don't need it).

Suppose I want to enter in the main record "The last track of this CD will play for 4:55 minutes."

I know that I could use the @FormResultSetTotal() command to find that there are, for example, 12 tracks.  Could I (with or without the use of this command) determine the "time" from the last record in my set?

In other words, how can I pick up the "Time" entry from track
12 and not from track 9 (or any other track)?

Thanks!

Quote:


Hello Spencer,

Something like

Var vTrackCnt as Int
Var vLastTrackTime as Double

vTrackCnt = @FormResultSetTotal("MySubformName")
vLastTrackTime = @FormFieldValue("MySubformName", "TrackLengthElement", vTrackCnt) 

-Ray

I have just spent many hours to get some code to work, and it is still not working.  Coming back to the forum for some hints/help, I find I am not alone working in this same area.  Code works with Enter, but not with mouse,
(or vice versa, I have already forgotten I have done it so many ways).

This has got to be the most confusing part of Sesame that I have encountered.  I don't think I am alone in thinking that the expectation is that Element Exit programming should run when you exit the element.  It should not matter if done with the mouse, with ENTER/Tab/Arrow.

If we must live with this, and it depends on the Mode, then I could use some explanation about which "Mode" is used.  There is a lot of inconsistency about the term Mode.

Quote:
Could you please explain Navigate Mode vs. Edit Mode vs. Preview Mode, vs. Add Mode, Update Mode, etc.  Page of Users Manual only list 4 modes -Search/Update/Add/Working.

Where is Navigate Mode?

I have spent many hours trying to get TableView SubForm code to execute to no avail.  Spencer has been having the same problem, Carl has been having the same problem.  I still have "basic" instructions that will not execute consistently.  We need to have easy to use tools that do not require extensive code just to do a simple ThrowFocus for example.

If this was for myself, maybe I could live with it.
If I am working for someone else and billing per hour, then my end user could not afford the programs.  Since I want to keep their cost down, then I must do this work at no charge so they can afford the product, but now I pay the cost in lost productivity.
If I am working on fixed cost vs. hourly, then I am losing many hours that could be billed for other tasks.

The quote above is probably a good start, but could someone please provide a decision tree that Sesame follows when exiting an element, using the same terminology that is in the Users Guide and Programming Guide?

Like this simplified model, but with all decision branches and the logical order that is followed:
What is the Mode?
If Mode = n then ........
If sub form then ......
If trigger to exit was Enter then ......
If trigger to exit was Mouse then......

We can continue to submit code examples and ask Ray to solve the problem, but it is more important that we have the information so we understand what is going to happen when an element loses focus. 
What about when Ray is not available like this weekend, or any other time?
We need to be able to write simple "click" routines that do complete tasks, and not have to add Calculate buttons to parent forms and rely on someones memory to click on a button.

Please understand, this should not be read as a complaint, but as a PLEA for easy to understand logic flow.  I don't think that Carl or Spencer or myself are beginners, but it is obvious that we are struggling with some stuf that should be really basic to do. 

Looking forward to see the logic flow......thanks for listening.

Thanks for reply Mark, but still not clear to me.

Quote:
RE "different form" in the quote above, is moving to a new record in the same subform the same as going to a different form?  I would be thinking NO.  If I moved to the parent form then I would think that is a different form.
When the mouse cursor is on an element, not opened to edit, and then clicks on an element in another record in the same subform will the Element Exit program execute?
Does using the mouse = "leaving the element"?
Does pressing ENTER = "leaving the element"?
Does using the UP/DOWN arrow = "leaving the element"?

Does this logic also apply to Forms as well as Elements?

If I use NotifyForm(1) in FormExit, why is it that I can keep pressing the Down Arrow and keep adding blank records into the subform?  Why is NotifyForm(1) allowing me to save a record and continue to add another one?  Are you saying the Down Arrow is Navigate Mode, and because I never opened the record that Edit Mode is never active?

Does this also mean the Form Entry does not fire either with the Up/Down arrows?  How about the Navigation buttons at the top of the form?

Quote:
Does color have anything to do with this.  If I just click once on a record LE I see no change.  I think I am in "Navigate Mode" based on these earlier explanations.  Now I click in the same LE in another record, I see no change.  Is this what you are calling "reverse"?  This seems normal to me, not reverse.  But when I make a second click, then I get black on white, "active" appearance for editing.  I would now guess that I am in "Edit Mode" ?

I am not trying to drag this out, I am just still confused.

If I go to a blank LE in a subform and Click the mouse for focus, nothing happens.  If I make a second click I get "Edit Mode" but programming in ImmediateChange is firing even though I have not entered anything into the element.  I would have expected ElementEntry programs to fire, but no Immediate Change.....nothing has been changed.  I can still exit this record and click in another record without making any change.

After all this time, I thought I had a handle on this but one I started proctecting against deleted records, I have found out that many of my understandings were probably not complete.  It is like I am releaning all over again.

Any chance for the Decision Tree that I requested for us?

I am really not trying to be picky here Mark.  It's not just words.  Words mean something.  "It depends what 'is' is".
Quote:


For years I have understood that "highlighted" meant that a group of characters had a distinct background color associated with the group.  Like when I "highlight" a group of characters to Copy/Paste.  I select the characters for the operation and they are highlighted.

On a subform I never see any "highlighted cell" in "Navigation" or "Edit" mode unless I am editing in a LE and select those characters as noted above.

Do you really mean highlighted, or are you meaning a reference to a LE that may have the LE block "outlined"?

Part of the explanation problem is the indiscriminate use of words that seem to have multiple meanings depending on one's past experiences.  I know that I make a conscious effort to use LE or element vs. field and application vs. database on Sesame forum.

So, if you mean that if an LE box is outlined in a Table View subform, that means we are in Navigate Mode, and ElementExit programming will not execute?  Do I have that correct now?

If NO, please try to explain again.
If YES, then what can be done to force Element Exit programming to execute in the outlined LE as one Navigates between the records in the SubForm?
Can we add StandAlone =0 to force execution in Navigation mode?

If this cannot be done, then does that mean we should not put programming in Element Exit LEs that are on SubForms?  Obviously NO, because we do want code executed when in Edit Mode.

If we are in Edit Mode, and use an arrow or mouse to exit from the LE, does that immediately put us into Navigation Mode and prevent the Exit code from executing?

Still listening?  Still willing to Help?  Thanks again.

Quote:

The problem I had, was that the On Element Entry event doesn't execute when ThrowFocus is responsible for navigating to the element. Navigating there manually with the mouse, it executes as expected, even though it is still not in 'edit' mode, just in 'navigate' mode.