Runtime Considerations for Component Interface Programs

Understanding Runtime Considerations for Component Interface
Programs
In many ways, accessing a component interface is functionally equivalent to working with an
online component. However, there are some important differences between component
interfaces and components. This section describes how those differences affect interactive
operation, functionality designed for graphical interfaces, client vs. server operation, and
several miscellaneous situations. These considerations, unless otherwise noted, apply to all
the programming languages listed in this manual.

This section discusses:
• General considerations
• Scope conflicts
• Interactive mode


General Considerations
This section discusses general considerations for component interface programs.

Saving a New Row
When you use the Create method, you must assign a value to at least one non-CreateKey
property to ensure that the Save method properly validates the row data. If you don’t assign a
value to at least one property, the Save method could erroneously save an invalid record
without generating any warnings.


WinMessage Unavailable
You can’t use WinMessage in a component that will be used to build a component interface.
Use MsgGet() instead.

Email From a Component Interface
To use a component interface to send email, use TriggerBusinessEvent PeopleCode event, not
`SendMail.