Hi,
i need to connect to Ingres DB, from .net (c#) - but not through ODBC, i
need to user direct access if possible
Can i use Oledb connection?
Do i need special data access adapter?
What is connection string?
the one i found:
Provider=MSDASQL.1;DRIVER=Ingres;SRVR=xxxxx;DB=xxxxx;Persist Security
Info=False;Uid=myUsername;Pwd=myPassword;SELECTLOOPS=N;Extended
Properties="SERVER=xxxxx;DATABASE=xxxxx;SERVERTYPE=INGRES";
was not really helpful, cause after filling xxxx-es, i got exception, maybe
i do not undrestand how to use this connectionString.
Thank you.
Gerhard Hofmann - 06 Dec 2006 20:06 GMT
> Hi,
> i need to connect to Ingres DB, from .net (c#) - but not through ODBC, i
[quoted text clipped - 12 lines]
>
> Thank you.
Ingres 2006 provides a DotNet Data Provider (ca.ingres.client.dll). The
Ingres Connectivity Guide describes how to use it, there is some C#
sample code included.
HTH
Gerhard
TheMaxx - 07 Dec 2006 07:35 GMT
How about Ingres 2?
>> Hi,
>> i need to connect to Ingres DB, from .net (c#) - but not through ODBC, i
[quoted text clipped - 19 lines]
> HTH
> Gerhard
Gerhard Hofmann - 07 Dec 2006 13:53 GMT
> How about Ingres 2?
You can take the ca.ingres.client.dll file from an existing Ingres R3 or
Ingres 2006 installation.
You can deploy the file onto client PCs *without* having to install
Ingres(Net), the dll alone is sufficient.
AFAIK (not sure about this), the DotNet data provider
(=ca.ingres.client.dll) can also connect to 2.x installations.
Regards
Gerhard
Paul Mason - 07 Dec 2006 15:06 GMT
> > How about Ingres 2?
>
[quoted text clipped - 6 lines]
> AFAIK (not sure about this), the DotNet data provider
> (=ca.ingres.client.dll) can also connect to 2.x installations.
Well actually no. The DotNet data provider connects to a Data Access
Server running in the target Ingres installation, so it needs to be r3
or above.
However what you could do is have an Ingres 2006 installation with a
vnode pointing to your 2.x installation. Then in the DotNet
application point to your 2006 DAS server but specify your database as
vnode::database.
At least I think that would work. I haven't tested it. I guess it
would depend on whether the DotNet provider uses any features in the
DBMS that are new since whatever version you're trying to connect to.

Signature
Paul Mason