ADODB And Ingres Database

[Colin Steadman]

I'm updating a template that currently uses DAO and an
Ingres ODBC DSN to connect to a database and retrieve
data. I would like to switch to ADODB but I'm unsure if I
can do this.

I've been looking at the Provider examples at -

http://www.able-
consulting.com/MDAC/ADO/Connection/OLEDB_Providers.htm#OLED
BProviderForSQLServer

But Ingres is not listed. Does this mean I can't use
ADODB to connect? Or is there some kind of generic
Provider that I could try?

If it helps, my connection code looks something like this
as it stands (bare bones version) -

==========================================================
Public ws As DAO.Workspace
Public cn As DAO.Connection
Public rs As DAO.RecordSet

Sub AutoNew()

Set ws = DBEngine.CreateWorkspace
("MyWorkspace", "admin", "", dbUseODBC)
Set cn = ws.OpenConnection("ODBCConnection",
dbDriverNoPrompt, _

False, "ODBC;DATABASE=live;UID=;PWD=;DSN=ingres_db")

SQL = "select this, that, other from table where this
= 'something'"

Set rs = cn.OpenRecordset(SQL)

'Now do somthing with the data.

End Sub
==========================================================

TIA,

Colin

 

[Lars-Eric Gisslén]

Colin,

As far I know there is no OleDB driver for Ingress (now called Advantage
Ingress) . You can look at this site and search for further information.
http://www3.ca.com/Solutions/Product.asp?ID=1013

You can however use ADO to access ODBC sources but I don't know if you would
get any advantage of that.

I have the developer edition of Ingress (even got the Jasmine OODB) as it
comes with my dev tool (CA product) and I've got only the ODBC driver.

Regards,
Lars-Eric

 

[Colin Steadman]

As far I know there is no OleDB driver for Ingress (now called Advantage
Ingress) . You can look at this site and search for further information.
http://www3.ca.com/Solutions/Product.asp?ID=1013

You can however use ADO to access ODBC sources but I don't know if you would
get any advantage of that.

I have the developer edition of Ingress (even got the Jasmine OODB) as it
comes with my dev tool (CA product) and I've got only the ODBC driver.

Regards,
Lars-Eric

Hi Eric,

Thanks for posting. I think I'll stick with what I've
already got if this is the case. There doesn't seem to
much point in changing it if I still have to use an ODBC
DSN.

Cheers,

Colin

 

[Lars-Eric Gisslén]

Colin,

There is an old saying in software development: 'If it works, don't fix it.'


Regards,
Lars-Eric