As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.
What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.
During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.
I experimented with that sort of thing in Maintain and I could not get it to function correctly. The example above is fully sufficient. Nice and clean -- create one edit field and then cut-and-paste to have the trigger appear and function correctly on all the edit fields on the page.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
This is one of my pet hates for Maintain. There is a level of control you do not get with on events. What I do, for example, is create my own controls in an HTML object, and put that on the form. The HTML is what I coded not what Maintain generates.