I am seeing the same thing here. The problem is that you don't have any other navigable elements before the TabPage group, so Sesame seems to prefer to start with focus on a command button rather than a TabPage, even though the navigation order may have the TabPage at the top of the list.

This is not perfect, but a workaround would be to put an unbound text field in the top left corner of the form. Make it 1 by 1 pixels in size, to keep it almost totally out of sight. This will allow Sesame to begin with focus on that element when the form first opens. Then, at least, you can get to the first element on the TabPage by pressing the tab key just twice.

Unfortunately, calling ThrowFocus() or GotoTabPage() from either the On Form Entry or On Retrieve Spec Open events doesn't seem to work in this case. (Though, ThrowFocus() will send focus to an element on a TabPage if it is called from another element's entry or exit event - just not immediately upon opening the form.)

Hi Carl and Bob...thank you very much.  Much appreciated!

I tried your suggestions and Sesame does first see my new "focus" field first, however, when exiting that field Sesame then points to the first command button obliging tabs through them all before we get to the first element of the the first tab page.

Using ThrowFocus() and GOTO from my "focus field" have no affect on the behavior at all.

I am likely missing a fine point somewhere and do thank you for your help.

Cliff

In "Set Navigation Order"; I have 13 "element groups" beginning with the form element group (POLICY) plus 12 tab pages.

In the form element group my new "FOCUS ELEMENT" shows at the top of the list followed by the first (of the six) button (SEARCH_UPDATE) and so on...

I don't know if this is helpful but the form element contains only the "focus element" and the six buttons I mentioned earlier.

I trided using ThrowFocus on exit to the first field of the first tab page which is "POLICY_NO" i.e., ThrowFocus(POLICY_NO) after your first direction to me and it appears to be ignored...

However, I just double checked this and it seems we are half way there.  If I open the form in "Add Data" mode the ThrowFocus does its job, however, if I open the form in "Search/Update" mode it does not.

I do appreciate you slogging through this tedium with me...

Again...thanks...

Cliff wrote on Mar 17^th, 2009 at 2:14pm:


When you say "Search/Update", do you mean at the Retrieve Specs (Search)?

Code in the On Element Exit (or On Element Entry)event will not execute at the Retrieve Spec screen. But, you should be getting the same results in Update mode as you are getting in Add mode, unless you are using a conditional statement that is preventing it (as lksseven pointed out).




BTW, as a side note, command buttons DO execute code in their On Element Entry event.

The only elements that should go on a tab page are those that are specific to that tab page. If an element is useful on every tab page, it should appear on the form itself, and thereby be available to every tab page.

I'm trying to tell you that your solution - putting the buttons on each of the tab pages, would lead to more problems, without regard for any changes that may have happened with the upgrade. I would try to find a different solution.

I thought I'd revisit this issue having some hours to do so.  What I have found is that there was some issue with the group / user security settings.  I removed all the security settings on the application and the "focus" issue was no longer an issue even without using additional code, i.e, "ThrowFocus()", etc.  I recreated security and all seems well.

So am "feeding back" to let any know what I found...

Thanks again...