WinBatch Technical Support Forum

Archived Boards => COM Automation and dotNet => Topic started by: stanl on July 04, 2013, 10:09:10 am

Title: CLR - OLEDB
Post by: stanl on July 04, 2013, 10:09:10 am
Appears the methods and properties derived from a single object in COM require multiple classes in .NET
...but for starters...
Code: Winbatch
;Winbatch 2013 - CLR - OLEDB {baby steps}
;
;
;Stan Littlefield July 4, 2013
;////////////////////////////////////////////////////////////////////////////////////////////////////////
ObjectClrOption("use","System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089")
oProvider = ObjectClrNew("System.Data.OleDb.OleDbConnection")
oProvider=0
Exit
 
 
Title: Re: CLR - OLEDB
Post by: DAG_P6 on July 04, 2013, 01:30:26 pm
Appears the methods and properties derived from a single object in COM require multiple classes in .NET
...but for starters...

I'm not sure what you mean.  Perhaps you are using the word "derived" in a different way. By derived, do you mean "Inherits From?"

The last time I did anything with ADO, whether it was in .NET or VBA, I needed a fistful of objects, most of which depended, directly or indirectly, on a ADO Connection object.
Title: Re: CLR - OLEDB
Post by: stanl on July 04, 2013, 02:29:08 pm
I'm not sure what you mean.