Opus DirectAccess Compatibility
Rubicon 2 officially supports the database engines listed on the drivers page. These engines provide virtual TDataSet
descendents so that all the products can be installed simultaneously as we perform quality
testing. Database engines that do not provide virtual TDataSet descendents are not
supported because of the added time it takes to reconfigure Delphi and C++ Builder during
development. Tamarack Associates has received several inquiries regarding ODA support, but because ODA does not provide a virtual TDataSet, it is not officially supported. However, ODA users have reported that they were able to use the Rubicon 2.03 TTable drivers with ODA with very minor modifications. Given this, changes were made to Rubicon 2.04 to make it compatible with ODA. What 'compatible' means is that Tamarack Associates will incorporate reasonable changes to the source code of Rubicon that allow it to work with ODA. These changes are always suggested by the ODA users as Tamarack Associates does not perform any ODA testing. The assumption is that if the Rubicon TTable driver uses standard TTable calls, that ODA should support them. While it is likely that all the components, utilities, and examples will work with ODA, compatibility should only be assumed for the core Rubicon 2 components: TrbMake, TrbUpdate, and TrbSearch. In order to use Rubicon 2 with ODA, the rb20bXXr.dpk and rb20bXXd.dpk (where XX is 30 for Delphi 3, 40 for Delphi 4, 50 for Delphi 5) run time and design time packages must be recompiled under ODA. The UseGotoKey compiler directive in rbDefine.inc should also be enabled for optimal performance. For instructions on how to recompile the packages, see the FAQ. ODA Feedback Ron Veerman wrote:
|
Copyright 2003 © Tamarack Associates |
||
www.TamarackA.com | Last updated 03/28/00 | www.FullTextSearch.com |