SalesLogix OLEDB Driver.

[Satish Itty]

I know this is more a Saleslogix issue than and .NET one. I thought I'll try
my luck here.

I'm trying to access Saleslogix database using SLXOLEDB driver in my .NET
application. This seems to work fine when I have the whole Saleslogix client
app installed on my computer. But when I have only the Saleslogix OLEDB
Driver I get an invalid case exception when I try to open a connection.
Here is the code snippet.
mConnString = "Provider=SLXOL EDB.1;Data Source=SLX01;In itial
Catalog=SALESLO GIX_DEV;Persist Security Info=True;Exten ded
Properties='Por t=1706;Log=On'; User Id='user';Passw ord='password'" ;

mConnection = new OleDbConnection (mConnString);

try

{

mConnection.Ope n();

}

Catch (Exception e)

{

Console.WriteLi ne(e.message);

}

finally

{

mConnection.clo se();

}

I was just wondering if anyone had come across the same problem. Any help
would be greatly appreciated. I have been banging my head against this for
the past 3 days :-(
--
Satish

[W.G. Ryan eMVP]

You may want to try Jeremy Brayton http://geekswithblogs.net/jbrayton/ - I
konw he does a lot of SalesLogix stuff

--
W.G. Ryan, MVP

www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
"Satish Itty" <NO_SPAMsitty@c laytonDOTcom> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

I know this is more a Saleslogix issue than and .NET one. I thought I'll try my luck here.

I'm trying to access Saleslogix database using SLXOLEDB driver in my .NET
application. This seems to work fine when I have the whole Saleslogix client app installed on my computer. But when I have only the Saleslogix OLEDB
Driver I get an invalid case exception when I try to open a connection.
Here is the code snippet.
mConnString = "Provider=SLXOL EDB.1;Data Source=SLX01;In itial
Catalog=SALESLO GIX_DEV;Persist Security Info=True;Exten ded
Properties='Por t=1706;Log=On'; User Id='user';Passw ord='password'" ;

mConnection = new OleDbConnection (mConnString);

try

{

mConnection.Ope n();

}

Catch (Exception e)

{

Console.WriteLi ne(e.message);

}

finally

{

mConnection.clo se();

}

I was just wondering if anyone had come across the same problem. Any help
would be greatly appreciated. I have been banging my head against this for
the past 3 days :-(
--
Satish