ADO and Oracle ODBC drivers
I would if I could, but it's not my decision. ODBC is the installed
standard on every machine where I work - I can't guarantee that OLE DB
drivers even installed anywhere. I suspect that Microsoft's Oracle OLE DB
drivers are there, but I don't know for sure - some users are still using
Windows 95 and might not have them.
If I were to try and get Oracle OLE DB drivers installed, I'd have to get
approval from the DBA's and Tech Support, and I'd have to figure out on my
own how to get them installed everywhere - even though I don't have to
install them. Unfortunately, that's just not going to happen - it will take
too long.
As it turns out, my process will work on the server - they have the correct
ODBC drivers. So for this time, I'm OK. What may help me out is that we're
going to Windows 2000 late this summer, so I might be able to sneak it in
the new image. We'll see what happens...
Thanks!
Scott
Quote:
> I know you mentioned you're using ODBC because that is your company's
> standard of accessing an Oracle database, but I encourage the use of the
> OraOLEDB.Oracle provider if you're going to be doing ADO.
> This works fine with Oracle 8i Release 2 (8.1.6) and Visual Basic 6 with
> Service Pack 5 on Windows 2000 with Service Pack 1.
> Here is my connection string:
> DatabaseCursor.ConnectionString = "Provider=OraOLEDB.Oracle;User
> ID=" & sUser & ";" & _
> "Password=" & sPassword & ";Data Source=" &
> sDatabase & ";" & _
> "DistribTx=0;"
> > I've been introducing myself to ADO at work, and I finally found a
project
> > where I can use the skills. However, I've run into something that I
can't
> > explain. This is my first "real" ADO project; my previous VB database
> > experience lies with DAO and RDO.
> > We use Oracle 8 here at work, and I have the Oracle 8 ODBC drivers
> installed
> > (ODBC is still the standard here, because we also have PowerBuilder
> programs
> > that can't use OLE DB). When providing the following connection string:
> > Data Source = ETOS;User id = <user ID>;Password = <password>;
> > where the DSN is set up using the Oracle ODBC drivers does not work.
> > However, if I set up a new DSN using the Microsoft Oracle ODBC drivers,
> and
> > pass the same connection string (with the new DSN name, of course),
> > everything is great.
> > What happens using the Oracle drivers is that the Recordset will open,
but
> > it returns no records (BOF and EOF are True), and accessing the
> .RecordCount
> > property throws an error ("Property 'RecordCount' of _Recordset object
> > failed").
> > This program is an automated FTP program that will not be running on my
> > machine, so I am not sure which set of ODBC drivers will exist. I need
to
> > be able to use both anyway, since other projects I will be working on
use
> > the Oracle ODBC drivers. What do I need to do to make those work?
> > TIA
> > Scott
