Worked at home today (Saturday), so no report on Ray or Erika.

I wrote a new SBasic subroutine: "FormRunProgram(form_name as string, le_name as string, event_number as int)" for Sesame 2.0 that runs the code attached to a different form's LE's. You specify the form name and the LE's name as strings, and the event number as an integer.

0 = LE_ENTER
1 = LE_EXIT
2 = FORM_CHANGE
3 = LE_CHANGE
4 = FORM_ENTER
5 = FORM_EXIT
6 = IMMEDIATE_CHANGE

So to run the on LE enter event on the Descriptions LE on the Gem Types form in the Gems applications from the Gems subform:

FormRunProgram("Gem Types", "Description" 0)

 

Quote:


The code runs right where it is on the form and LE it is actually attached to. That form must be open. The form specified cannot be the current form, it must be a different form.

This was written largely to ease inter-form communication and notification. For example, to notify the parent form that a condition on one of its subforms needs its attention / recalculation.

Thanks. Unlike most software companies, Lantica is comprised of companies that do consulting using Sesame/Q&A. It gives us a very direct line on the most pressing needs (as does this Forum) of the folks developing applications using Sesame.

This subroutine came directly out of some consulting work Hammer is doing that involves an application with about twenty subforms and thousands of LEs. In this case the main form needs nearly constant updates based on data from the subs.