RCB allows you to choose between seven different database access modules: DB2 CLI, Microsoft SQL Server, MySQL, ODBC, Oracle OCI, PostgreSQL, and Sybase. When installing any of these access modules, as well as its examples, you must specify a number of fields to allow your examples to connect to a relational database server with a valid user name and password.

While each of the DB Access Modules prompts have minor differences, they follow the same pattern as the screen below.

To connect your examples to the database, you must provide all required connection information. The table below lists all the potential fields that may be used when installing a DB Access Module.

If you have any questions about the required options, see the access module user’s guide, located at buildspace\docs\html\<access-lib-mnemonic>ug. For example, the Oracle OCI user guide is located at buildspace\docs\html\oracleociug.

You can also access any of the documentation from the general index at buildspace\docs\html\index.html.

Information on environment variable settings for the various database clients can be found in the Building Your Applications.

For MS SQL Access Module, there is an extra option, SQL Server Client, which can have following values:

If the last two options are selected, the path to the SDK needs to be entered on the following screen.

If the build of the examples failed because of incorrect information entered for the database connection parameters, you must delete the examples directory where the failed build results were placed before you rebuild the examples. For example, if you attempted to build examples for ODBC in the 8s configuration and the build failed, you must first delete buildspace\examples\odbc\8s before you can rebuild the examples.

If you do not delete the directory, RCB fails to re-parse the connection information and continues to use the erroneous information, resulting in another failed build.

Alternatively, to rebuild the examples, do the following. Go to the build directory (for example, buildspace\examples\odbc\8s), edit the file tutdefs.h and update the values. Execute the make clean (or nmake clean) command, and then execute the make (or nmake) command.