Re: Multi Tiered ODBC

Andrew Mills <andy_mills@dial.pipex.com> wrote in article <andy_mills-1111962143190001@an208.du.pipex.com>... > In article <327DE5D2.57DD@businessobjects.com>, > wmartin@businessobjects.com wrote: > > > I would love to hear some feedback from anyone who has had experience > > using a multi tiered ODBC solution (like OpenLink for example) to > > connect to a variety of RBDMSs. I am especially interested to know what > > experience people have had targeting SQL to one ODBC client and > > successfully creating tables with complex datatypes in multiple RDBMSs. > > Any input would be appreciated. > > Intersolv provide multi-tiered client-server software solution 'SequeLink' > SequeLink is a multi-platform heterogeneous middlware solution. Intersolv > can be contacted at www.intersolv.com. > Please be aware that the word "multi-tier" means something quite different when applied to ODBC. A two-tiered ODBC corresponds to a flat file database. A three-tiered ODBC corresponds to the old two-tiered client/server (application<->ODBC driver<->RDBMS). And in general, whenever the ODBC documentation mentions the word "tier", no "three-tiered client/server application" meaning is intended. Targetting multiple RDBMSs with ODBC sounds like a noble thing to do, but doesn't offer any advantage to the corporate developers who have endured a painful process of selecting their RDBMS very carefully. Shrink-wrapped applications would benefit from the "we can use any RDBMS as long as it has ODBC" slogan. I have yet to see a serious application that is PURE ODBC. My favorite ODBC related message---"Driver Not Capable." -- Weiqi Gao weiqigao@crl.com