Showing posts with label adonet. Show all posts
Showing posts with label adonet. Show all posts

Tuesday, March 20, 2012

Programming with OLEDB and ADO.NET

Hi
I currently use OLEDB in my C++ application to connect to MSSQL. I am
considering moving to ADO.NET.
Is there a document outlining the difference between them?
Lawrence
Lawrence,
I have posted a couple of links below one of which is a comparitave overview
of ADO and ADO.net and the other is data retrevial and modification using
ADO.net. OLEDB is still a part of ADO but you now have access to native SQL
in the SQLClient namespace (that is if you are using Sql Server).
Hope this helps.
http://msdn.microsoft.com/library/de...etprogmsdn.asp
http://msdn.microsoft.com/library/de...WithADONET.asp
|||Lawrence,
I found another link with a good article of the evolution of the data access
model. This may give you a better understanding in the change of the model
from OLE DB to ADO.net.
Good Luck.
http://msdn.microsoft.com/library/de...asp?frame=true
|||Thanks for these articles.
They did not really help me. They refer to using OLE DB with a COM interface.
I did not go that direction using C++ but used the API.
Lawrence
"Brian Brown" wrote:

> Lawrence,
> I found another link with a good article of the evolution of the data access
> model. This may give you a better understanding in the change of the model
> from OLE DB to ADO.net.
> Good Luck.
> --
> http://msdn.microsoft.com/library/de...asp?frame=true
>
|||Lawrence,
I am sorry that this information did not help you. Maybe I have
misunderstood what you are wanting to do. Is there something specific that
you are trying to accomplish that you have a question about?

Programming with OLEDB and ADO.NET

Hi
I currently use OLEDB in my C++ application to connect to MSSQL. I am
considering moving to ADO.NET.
Is there a document outlining the difference between them?
LawrenceLawrence,
I have posted a couple of links below one of which is a comparitave overview
of ADO and ADO.net and the other is data retrevial and modification using
ADO.net. OLEDB is still a part of ADO but you now have access to native SQL
in the SQLClient namespace (that is if you are using Sql Server).
Hope this helps.
--
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/adonetprogmsdn.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconAccessingDataWithADONET.asp|||Lawrence,
I found another link with a good article of the evolution of the data access
model. This may give you a better understanding in the change of the model
from OLE DB to ADO.net.
Good Luck.
--
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sqlserverprog.asp?frame=true|||Thanks for these articles.
They did not really help me. They refer to using OLE DB with a COM interface.
I did not go that direction using C++ but used the API.
Lawrence
"Brian Brown" wrote:
> Lawrence,
> I found another link with a good article of the evolution of the data access
> model. This may give you a better understanding in the change of the model
> from OLE DB to ADO.net.
> Good Luck.
> --
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sqlserverprog.asp?frame=true
>|||Lawrence,
I am sorry that this information did not help you. Maybe I have
misunderstood what you are wanting to do. Is there something specific that
you are trying to accomplish that you have a question about?

Programming with OLEDB and ADO.NET

Hi
I currently use OLEDB in my C++ application to connect to MSSQL. I am
considering moving to ADO.NET.
Is there a document outlining the difference between them?
LawrenceLawrence,
I have posted a couple of links below one of which is a comparitave overview
of ADO and ADO.net and the other is data retrevial and modification using
ADO.net. OLEDB is still a part of ADO but you now have access to native SQL
in the SQLClient namespace (that is if you are using Sql Server).
Hope this helps.
--
http://msdn.microsoft.com/library/d...netprogmsdn.asp
http://msdn.microsoft.com/library/d...aWithADONET.asp|||Lawrence,
I found another link with a good article of the evolution of the data access
model. This may give you a better understanding in the change of the model
from OLE DB to ADO.net.
Good Luck.
http://msdn.microsoft.com/library/d...asp?frame=true|||Thanks for these articles.
They did not really help me. They refer to using OLE DB with a COM interface
.
I did not go that direction using C++ but used the API.
Lawrence
"Brian Brown" wrote:

> Lawrence,
> I found another link with a good article of the evolution of the data acce
ss
> model. This may give you a better understanding in the change of the mode
l
> from OLE DB to ADO.net.
> Good Luck.
> --
> http://msdn.microsoft.com/library/d...asp?frame=true
>|||Lawrence,
I am sorry that this information did not help you. Maybe I have
misunderstood what you are wanting to do. Is there something specific that
you are trying to accomplish that you have a question about?

Wednesday, March 7, 2012

Programmatically Adding ADO.NET Connections

I can't find any documentation on the connection string for creating ADO.NET connections.

I am displaying a report in a viewer. It is connected to a wrapper DLL through an ADO.NET connection using the properties:
File Path
Class Name
Dataset Names

I'm having trouble accessing these to change them at runtime.

I've tried something like:
rpt.database:Tables(1):ConnectionProperties("File Path") = "c:\..."

No luck. Crystal doesn't have much documentation on this method. Any takers?Nevermind. Got it.

I was able to override the path of my DLL at runtime using the syntax:

report.database.tables(1).ConnectionProperties("File Path").Value = "c:\blah"

seems to be working.