What could be the possible cause of this problem?

The Orders application enables the Orders form to be opened from the Customers form. Users are
confused because when they save a new or changed order, they sometimes receive an error
message that indicates that no changes have been made.
What could be the possible cause of this problem?

A.
The Orders form is Openedinthe same session as the Customers form.

B.
The Orders form is openedina different session from the Customers form.

C.
The Orders form is openedinACTIVATE mode.

D.
The Orders form is openedinNO_ACTIVATE mode.

E.
The trigger that opens the Orders form calls COMMIT_FORM after open form.

Explanation:
If you want to end the current transaction before opening the next form, call the
COMMIT_FORM built-in before OPEN_FORM. You can check to see if the value of
SYSTEM.form_status=’CHANGED’ to decide whether a commit is needed. Alternatively, you can
just post changes to the database with POST , then open the nextform in the same transaction
Note: Control and Transactions WhenOpening Another Form
When you use
OPEN_FORM
* By default, control passes immediately to the Orders formand no statements after
OPEN_FORM are processed
* If the Activate_Mode argument is set to NO_ACTIVATE
,you retain control in the current form
* The transaction continues unless it was explicitlycommitted before