Parts are encapsulations of C++ classes used specifically for visual programming or database access. In VisualAge C++, the Visual Builder and Data Access Builder components use parts to support application development. Physically, parts are source files. Visual Builder visual or nonvisual parts are source files with the extension .vbf or .vbe. Data access parts are composed of a data access session file, a source file with the extension .dax, and one or more Visual Builder parts. You create visual, nonvisual and data access parts for your project using the Parts or Data Access Builder SmartGuides.
You can work with visual, nonvisual, and data access parts in the IDE. The Parts page and Data Access Builder Sessions page in the Project section of the workbook contain views where you can do the following:
If a part is the input object for the Classes or Files views in the Project section, these views list the classes and source files for the part.
Parts are added to the configuration file as source files. When the build process encounters a part in the configuration file, the Visual Builder or the Data Access Builder are notified to generate the source for the part if changes have been made.
Search Paths for Visual Builder Parts
If a project uses Visual Builder parts files stored in directories other than those specified for a project, the search path for those parts must be set in the INCLUDE environment variable. That is, if you have set the incl(searchpath) option in a Configuration view in the IDE, but have not set the INCLUDE variable, the .vbf file(s) will not be found. This does not apply to Data Access parts.
![]()
Integrated Development Environment
Data Access Builder Workflow
Visual Programming Fundamentals
![]()
![]()
Add a New Part
![]()
Add an Existing Part to a
Project
![]()
Edit a Visual or Nonvisual
Part
![]()
Edit a Data Access Part
