Migration Considerations

Saved sessions from the previous releases of Data Access Builder can be loaded into the new release. However, there are differences that you should be aware of:

  1. Visual Builder (.vbe) files are no longer generated. When Data Access Builder generates code, it will always generate parts that are usable for visual composition. These parts are loaded as part of the project.
  2. SOM (.idl) classes are no longer generated or supported with this release of the product.
  3. You must create a project in the IDE to compile and run the application that uses the Data Access Builder generated code.

You do not have to modify existing C++ applications that use the generated code from the last release of our product. However, to use the new Data Access Class Library, you have to import the session (.dax files) used by your C++ applications and regenerate the source code. Then you have to recompile and bind these applications before using them with the new class library.

By following the instructions on importing Data Access Builder sessions, you can import .dax files from the following VisualAge Products:

ngaix.gif (1051 bytes)Data Access Builder cannot import .dax files from VisualAge for C++ for OS/2 v. 3.0 because they are binary encoded.   Only ASCII text .dax files can be imported.



Data Access Builder


Migrate Existing Code
Import a Data Access Builder Session