Re: Installing ODBC on Windows 95

Ariel Kirson wrote:

> My company works extensively with Oracle 7 running
> on various Unix-based machines. We would like
> to allow our end users to connect to our databases
> using their own third party tools and for this reason
> we would like to provide them with ODBC support
> at the time that we install our Client application on their
> PCs.
>
> What drivers, DLLs, files etc. do I need to install and where ?
> (I have been told that SQLNet is a must, how is this installed?)
> Is this task easily automated so as to allow for it's incorporation
> into our own installation scripts ?
> Where can I get detailed information on this topic ?
> Am I correct in assuming that installing ODBC will allow
> connection to our DB through Excel, Access etc. ?

In our product SQL-Retriever (or SQL-Retriever Lite), we can provide an ODBC driver that provides all you need and that you can install with your application (the DLLs etc). We connect to Oracle7 on various UNIX platforms. We DO NOT NEED SQL*Net (and are therefore a lot cheaper than the Oracle solution): we provide all that is necessary to make the connection to Oracle.

Any ODBC-compliant app (e.g. Access, Excel, Word) will link to an ODBC driver anyway.

Try our ODBC driver: SCO SQL-Retriever. Take a look at http://www.sco.com/vision/products/sqlretriever/ for more information and a downloadable eval.

To briefly answer a couple of other points from the other existing posters on this thread:
ODBC was never reallly conceived to cope with vast results sets (100,000 rows): it will work, but the performance will not be impressive. It's partically to do with the way ODBC builds of the transport.

If your using ODBC across the MS Jet (which most of the MS apps do), the Jet requires a unique index on any table that is to be updated (mainly so that it can work out where it is in the table e.g. for an insert).

HTH Allan Gould
(allang at sco dot com)
(Please remove anti-spam measures if replying) Received on Wed Sep 30 1998 - 04:36:57 CDT