Consultor Eletrônico

Status: Unverified

GOAL:

Dynamics Object Naming Conventions

FACT(s) (Environment):

Dynamics 2.0A

FIX:

Dynamic objects use the same naming conventions as tables. Within the repository, the default dynamic SmartDataBrowser? with all table fields displayed is called rycagfullb. You can give other Browsers other names ending in b. In this way a sorted listing of filenames or object names (or both together) automatically groups together procedures and objects pertaining to a particular table; a standard name completion makes it easy to identify the type of object.


NOTE: This convention is the reverse of the standard ADM2 convention of beginning filenames with a letter or more that identifies the type. Either kind of convention can work; having a standard and being consistent with it is the important goal. Using the Dynamics standard for new databases and applications is appropriate simply because it is the standard chosen for the repository and the
procedures and objects that support it.


Dynamics keeps track of both static (procedural) and dynamic (data-driven) objects in its repository. In the case of a dynamic object, all the data needed to define and generate the object at runtime is stored in the repository. The object is given a name (such as rycagfullb) that is simply a key for locating the object; it does not correspond to any physical source file. Procedural objects are also registered in the repository, even though they are run as Progress r-code. These objects have a name in the repository that is the simple filename of the procedure without any pathname information and without the filename extension.
The relative pathname and filename extension of a procedural object are stored in different fields from the object name. In this way there is no significant difference between the name of a static versus a dynamic object. Therefore, you can convert a static object into a dynamic object in the future without disrupting its use within the application.