I am converting a complex Q&A payroll application to Sesame for a School Bus company.  There are many Layout Elements in an extra long page.  To make it more user frendly, I have used tabbed pages to organize the Xlookups and many data entry elements, as well as elements for display and review; thus avoiding trying to cram everything into one page.

At the end of each of the first two tab pages there is an element with code and a GOTO "on element exit" directing to the first element on the next page. (I want the data entry person to enter data in that last element.) Then the sequence simply stops, unless I click on the tab for the next page.

My workaround solution was to put a "dummy element" following that last element on the page, and using a GOTO "on element entry" from that "dummy element."  I then minimized that dummy element until it is hardly noticeable, and directed the previous element (on element exit") to it.

The sequence then goes automatically from those previusly "last elements" to the first elements on the next tabbed pages.

This sounds like a "Hokey" fix, but it works.  I think there should be a better way.  ...or am I having another "Senior moment"??

Thanks for the throwfocus idea.  I will try it out. 

I also discovered that an LE can be made invisible, which could work with my "dummy LE' idea.  (Visibility(x,n)) page 36 in the prog manual.

Jack

This looks like a good place for "accelerator keys". 

Many other products allow naming like "&History" and "Ma&ps" that result in History and Maps to be presented and that allow ALT-H and ALT-p to execute the same functions that would occur as if they were clicked on. 

Any chance that we can see Accelerator Key capability built into the labels/names for elements and even the names of other objects that are on the Trees?

This ability to use accelerator keys also reduces the need for operator to switch back and forth betrween keyboard and mouse, and makes it easier to create macros with third party utilities.