Re: ODBC with Oracle and Informix on the same server.
Posted in 1993
Someone (Jim Gordon?) said: > |> Unfortunately your consultant is basically correct. ODBC is a > |> translation mechanism to provide a single interface to client tools > |> requiring access to heterogeneous databases. It is NOT a network > |> product capable od doing the end to end communication between the > |> client and the server. So for Informix you would have Online or S.E + > |> I-Star on the Server, I-Net, ODBC and Access on the PC-Client. > |> I-Star/I-Net handle the network traffic ODBC handles the translation. > Steven Reiss asked: > Is this really true? I was under the impression that one could run the > ODBC code (i.e. the interface sw provided by a vendor) and have the > application > send ODBC calls across the network by itself, or possibly have it's own > software > on the server which could then talk to the ODBC sw. > > I am only speaking from a very high-level understanding of ODBC, not as a > developer. Sorry if this gets a little repetitive, but my understanding is that ODBC itself is not network-aware. Its original purpose was to allow your ODBC-compliant application to access a database _on_the_same_PC_ without depending on which brand of database software you had (provided that the database software was also ODBC-compliant). Thus, for the networking, you need a local piece of the database software (in the original scenario: SQL*Net or I-Net) for the ODBC driver to communicate with. This local piece (xxx-Net) would handle the networking to communicate with the database server. Any corrections to my comments above would be greatly appreciated. -- Bryan Klopfenstein bryan@carsinfo.com CARS Information Systems Corp. Cincinnati, OH Standard Disclaimers Apply