Class Description A short description or name for the class. You can enter up to 100 characters, using any combination of letters or numbers. The text you enter here will be used throughout the user interface to identify the class. It is not used in the generated code. See Also Class Name The class name to be used in any C++ code. This name cannot include spaces or punctuation. See Also Base Class The base class used for this class. Many classes inherit characteristics from base classes, such as Persistent, File, and Document. All classes exist in a variety of systems. If your new class inherits from a base class, this field will indicate the name of that class. APM supports single inheritance only. See Also DB Schema This check box enables you to indicate whether or not the class includes database schema. A class with DB schema adds and saves attributes and relationships to the database. See Also Table Name This field enables you to indicate the name of the SQL table that will contain instances of this class. See Also Primary Locking Object This check box indicates whether the class is a primary locking object. Whether or not an class is a primary locking object affects its locking behavior and the kind of user interface you can create for it. Primary locking objects can be locked individually. When a primary locking object is locked, all of the secondary objects it owns are also implicitly locked. Non-primary locking (secondary) objects, on the other hand, cannot be locked individually: they must be locked through their primary locking object parent. Primary locking objects can have both primary window views and dialog views. Secondary objects can only have dialog views. You can change this field at any time. However, if you change the object from a primary locking object to a secondary object, any main window views that you have defined for the object will no longer be accessible at run-time. See Also User Key This check box indicates whether or not this class has a user key. A user key is a unique name or a number used to identify each instance of this class. For example, the user key for a Customer object may be the Customer's Name and the user key for a Purchase Order might be the Purchase Order Number. When you define the attributes for this class, you will need to identify the attribute that is the class's user key. See Also Generate User Key This box shows whether or not APM should generate a user key for this class. A check in the box means APM will create a user key based on the format you enter. See Also User Key Format The format for the user key when you select the option to have APM generate the user key. See Also
