OK, now to properly place the pieces that do the communication magic! Inside the Omnis Studio 3.3 folder that was installed in the previous step, there are two folders that are important for this process. One is named external and the other is named xcomp. DAMs and other files we downloaded from the OpenBase and FrontBase sites need to be copied into these folders as follows:

For OpenBase, drill down into the OpenBase_DAMs_1.1.3.6 folder through the following hierarchy of folders: OpenBase_DAMs_1.1.3.6>Release DAMs>for Omnis Studio>Mac OS X. At this point, you will see two folders. The contents of the into external folder should be copied into the external folder in your Omnis Studio installation. The contents of the into xcomp folder should be copied into (you guessed it!) the xcomp folder of your Omnis Studio installation. When this has been accomplished, Omnis Studio will be able to communicate with OpenBase.

OpenBase External Files Installation

For FrontBase, the process is a bit simpler. We drill down through the folder hierarchy of FrontBaseV3DAM15>Mac OS X (Studio 3.x)>INTO Omnis-xcomp and copy the file we find there named FrontBase DAM (Mac OS X) into the xcomp folder of the Omnis Studio installation. Omnis Studio can now also communicate with FrontBase.

FrontBase External Components (xcomps) Installation

Now all we have to do is create a generic SQL Session Template for each SQL platform. While this is certainly an optional step and is only useful in the SQL Browser utility of Omnis Studio, it is a very useful optional step that can save us time and trouble down the road. It is well worth the minimal effort it requires. It also gives us a chance to become familiar with the SQL Browser...