Release 10.1A: OpenEdge Development:
AppBuilder

> ## Procedure settings

> Broadly speaking, procedure settings deal with the nonvisual aspects of objects that are based on external procedures. In the case of a SmartWindow, for example, they are aggregated into seven groups, each represented by a dialog box discussed in this appendix:

> - Main (this section)

> - Advanced procedure settings

> - Method libraries

> - Custom lists

> - Temp-tables

> - SmartLinks

> - Pages

> Other procedure based objects, including other SmartObjects, will have a different number of groups, depending on their nature. For example, a SmartDataObject will not have a Pages button because it is not a SmartContainer and thus does not support a paging context of its own.

> To open the main Procedure Settings dialog box for a procedure-based object, you must first open the master object itself, if there is one. Choose File Open and select the object or, if the object is a SmartObject instance, click the menu button and choose Edit Master.

> When the master object is open and selected, choose Tools Procedure Settings, or the Procedure Settings button from the toolbar. A dialog box similar to that in Figure A–4 opens.

> Figure A–4: SmartWindow main procedure settings dialog box

> The main Procedure Settings dialog box is used for all procedure level objects. Some of the fields will therefore not apply to a particular object type, either because the qualities are predefined and fixed, or because they are entirely irrelevant. The settings shown here are those for a SmartWindow:

> - Type — Reflects the type of subprogram being used for this object. Although you can reset this value in the Advanced dialog box, see OpenEdge Development: ADM and SmartObjects for more information.

> - File Name — Reflects the name of the `.w` file on disk. This is undefined until you save the object. You can change this value at any time with the usual MS-Windows tools—the Explorer file system interface, for example.

> - Description — A general-purpose, multi-line field for comments about this object.

> - OCX Binary — If you include any ActiveX objects in your SmartContainer's population, their properties are saved in a file, by default the `.w` file itself. If you prefer, you can specify a different file here.

> - Compile in — By default, the `.r` object file that results from compilation will be stored in the same directory as the `.w` source. If you prefer, you can specify a different directory here.

> - Run Persistent from AppBuilder — Determines whether the object procedure will preserve their data and interface contexts when the `RUN` statement that invoked them completes execution. Persistent contexts remain allocated until explicitly released, or until the end of the OpenEdge session.

> In general, you should check this box for all SmartObjects other than SmartDialog.

> - Compile on Save — Determines whether AppBuilder produces an object file when it saves the current source file, rather than recompiling whenever an instance is needed at run time. Checking this box is generally better, but because AppBuilder automatically compiles whenever changes are made, the advantages are not clear-cut.

> - AppServer Aware — Determines whether AppBuilder includes the header files required for connecting to an AppServer service, making requests of the service, and later disconnects from the service. In an ADM-compliant application, AppServer awareness is a property of the SmartDataObject, and generally not needed by other objects.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095