Guidelines for Including Escape Code
You can include most 4GL statements in your escape code. However, be aware of these restrictions and implications:
• Do not use begin-end loops that span escapes.
For example, do not put a begin statement into a Field-Entry escape and the corresponding end statement into a Field-Exit escape.
• Do not include a set autocommit on statement.
• Do not issue an initialize statement in escape code for a frame, because the Vision code generator always creates this statement for the frame.
• Do not use activation blocks—such as Menu item or Field activations—in escape code.
However, you can use submenus and queries with attached menus.
• Any escape code that you indicate for a particular menu item or field supercedes escape code specified with the ALL option (described below) for all menu items or fields of a frame.
• If you write escape code that calls another frame, the called frame does not appear on the Application Flow Diagram.
• If you use database (update, delete, select, and insert) statements in your escape code, include error checking code to ensure the data in your database is being updated correctly.