In general, form field objects can be selected to be active for all event types except the "Closed" event (see About Callback Events). However, not all event types are applicable to every form field type. For example, the "Modified" event is not applicable to an image form field as the data associated with this type of form field (i.e. the image file name) cannot be modified by the application end-user.
Field events, when inter-dependent, are triggered from "inside" the field to "outside" the field. Events internal to the field are always completed before events external to the field. Given that two events qualify as internal and are triggered simultaneously, the event that is more field-dependent is triggered first. For example, consider a field that contains the events "Modified" and "Lost Focus". Assuming that this field also has the attribute "Auto Skip" (the field looses the focus when the last character is typed in), each keystroke triggers an event, but the last character triggers both events (the "Modified" and the "Lost Focus"). In this case, the "internal" event takes precedence- the "Modified" is triggered first and the "Lost Focus" is triggered second.