re: .net, dotnet connect via System.Data.OleDb MSDASQL.1
 
Thanks for your assistance Marcin, unfortunately it is NOT working for me yet ;-).  My 
connection string is below, I have tried several variations of it all yield the same 
error (see below). Unfortunately I have the vb.net Visual Studio STANDARD edition and 
cannot use "Server Explorer" with Microsoft OLE DB Provider for ODBC Drivers - it is 
restriced to MSDE and Access and MS SQL. I am hoping this only is disabled in VS 
Studio. I am assuming with the right connection string I can successfully connect in 
code.
 
"Provider=MSDASQL.1;Persist Security Info=False;User ID=CM;Extended 
Properties='DSN=Contact;UID=CM;pwd=mypass;SERVERDB=CONTACT;SERVERNODE=192.168.32.##;'"

The error message is as follows: The .Net Framework Data Provider for OLEDB 
(System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers 
(MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc). 

I know ODBC works and the Interop assembly in .net works ok as well I was just hoping 
to be able to take advantage of the new .net syntax like datasets etc...
 
I am assuming you actually tried a compiled-code connection, perhaps the "server 
explorer" piece works but an actual compile via the framework might yield the same 
error I listed above.
 
I would love to hear from anyone who successfully develops using .net with MAXDB/SAPDB 
via the Microsoft OLE DB Provider for ODBC Drivers.
 
Thanks again....
 

Marcin P <[EMAIL PROTECTED]> wrote:
Yes, it's true that Ado relies on OLEDB.

There is a possibility to use Microsoft Oledb Bridge
for ODBC - I didn't use it as long as Odbc works fine on my site.
In your example, it seems to me that you're trying to connect
to SAP DB/MaxDB with Oledb Driver for MS SQL.
Try building ConnectionString with Server Explorer (from VS), and
choose Microsoft OLE DB Provider for ODBC Drivers.
I gave it a trial a moment ago and the result is:
Provider=MSDASQL.1;Persist Security Info=False;User ID=MY_USER;Data
Source=MY_DB;Extended
Properties="DSN=MY;UID=MY_USER;SERVERDB=TEST_DB;SERVERNODE=MACH_IP;"

It works OK.
However, as there is no native Oledb driver for
SAP DB/MaxDB you can always go with simple
ODBC classes.
m_cnADOConnection = New OdbcConnection()

Best regards,

Marcin Pytel
MCSD ;-)

Uzytkownik "H" napisal w wiadomosci
news:[EMAIL PROTECTED]
>
>
>
>
> Using asp and vb.net I very successfully am able to use ADO technology
with MAXDB database.
>
>
> I am confused though, in diagrams I have seen published by WROX ADO relies
on OLE DB technology. Why is it that I can't seem to get to the data using
the native OLE DB .net provider defined in the .net namespace known as
System.Data.OleDB (please provide an explanation or clear my confusion on
the technologies involved here).
>
>
> Where I am getting hung up is on the line of code below, I dont know what
I should put in the provider parameter. What I have there now I think is
exclusively for SQL-SERVER but I am not sure.
>
> stringConnectionString = "Provider=SQLOLEDB;dsn=contact;user
id=CM;password=*****;"
> objConnection = New
System.Data.OleDb.OleDbConnection(stringConnectionString)
>
> Is this possible? Has anyone done it?
>
>
> If it is not supported are there plans by MYSQL or Microsoft or anyone
else to achieve this?
>
>
>
> Thanks in Advance.
>
>
>
>
>
> ---------------------------------
> Post your free ad now! Yahoo! Canada Personals
>




-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]




---------------------------------
Post your free ad now! Yahoo! Canada Personals

Reply via email to