p2p.wrox.com: Archives - ado

ado_dotnet thread: DataReader

Message #1 by "marc cardenas" <marclena@h...> on Thu, 20 Feb 2003 16:10:49

Hi,
I am using a datareader to read a couple of records.
Then I'm trying to insert something on the database with the command 
object using the same connection than the datareader and I get an error 
message saying that I cannot use it because is a datareader open for that 
connection.
Cannot I have different datareaders pointing to the same connection.
Thanks

Message #2 by "Ted Nandakumar" <TedN@i...> on Thu, 20 Feb 2003 21:29:00 +0530

You cannot use the same connection object, till you close your 
datareader. This is by design.





-----Original Message-----
From: marc cardenas [mailto:marclena@h...]
Sent: Thursday, February 20, 2003 9:41 PM
To: ADO.NET
Subject: [ado_dotnet] DataReader


Hi,
I am using a datareader to read a couple of records.
Then I'm trying to insert something on the database with the command
object using the same connection than the datareader and I get an error
message saying that I cannot use it because is a datareader open for 
that
connection.
Cannot I have different datareaders pointing to the same connection.
Thanks
=3D=3D=3D
Fast Track ADO.NET with C# is a concise introduction to the concepts, 
techniques, and libraries that you will need in order to start using 
ADO.NET in your applications. The book covers DataSets and Typed 
DataSets, accessing data using DataReaders and DataAdaptors, the close 
relationship between ADO.NET and XML, how and where to use ADO.NET in 
your enterprise applications, and how to use Web Services and ADO.NET to 
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm

Message #3 by "marc cardenas" <marclena@h...> on Thu, 20 Feb 2003 16:22:56

But then if I want to work with the transaction object of the connection 
object how can I link the transaction between different connections?
Thanks
> You cannot use the same connection object, till you close your 
datareader. This is by design.





-----Original Message-----
From: marc cardenas [mailto:marclena@h...]
Sent: Thursday, February 20, 2003 9:41 PM
To: ADO.NET
Subject: [ado_dotnet] DataReader


Hi,
I am using a datareader to read a couple of records.
Then I'm trying to insert something on the database with the command
object using the same connection than the datareader and I get an error
message saying that I cannot use it because is a datareader open for 
that
connection.
Cannot I have different datareaders pointing to the same connection.
Thanks
=3D=3D=3D
Fast Track ADO.NET with C# is a concise introduction to the concepts, 
techniques, and libraries that you will need in order to start using 
ADO.NET in your applications. The book covers DataSets and Typed 
DataSets, accessing data using DataReaders and DataAdaptors, the close 
relationship between ADO.NET and XML, how and where to use ADO.NET in 
your enterprise applications, and how to use Web Services and ADO.NET to 
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm

Message #4 by "Ted Nandakumar" <TedN@i...> on Thu, 20 Feb 2003 21:45:54 +0530

you can try it using a dataset instead of a Datareader. DataReader is by 
default set to hog the resources of the connection, till it is 
destroyed.



-----Original Message-----
From: marc cardenas [mailto:marclena@h...]
Sent: Thursday, February 20, 2003 9:53 PM
To: ADO.NET
Subject: [ado_dotnet] RE: DataReader


But then if I want to work with the transaction object of the connection 

object how can I link the transaction between different connections?
Thanks
> You cannot use the same connection object, till you close your =3D
datareader. This is by design.=3D20





-----Original Message-----
From: marc cardenas [mailto:marclena@h...]
Sent: Thursday, February 20, 2003 9:41 PM
To: ADO.NET
Subject: [ado_dotnet] DataReader


Hi,
I am using a datareader to read a couple of records.
Then I'm trying to insert something on the database with the 
command=3D20
object using the same connection than the datareader and I get an 
error=3D20
message saying that I cannot use it because is a datareader open for =3D
that=3D20
connection.
Cannot I have different datareaders pointing to the same connection.
Thanks
=3D3D=3D3D=3D3D
Fast Track ADO.NET with C# is a concise introduction to the concepts, 
=3D
techniques, and libraries that you will need in order to start using =3D
ADO.NET in your applications. The book covers DataSets and Typed =3D
DataSets, accessing data using DataReaders and DataAdaptors, the close 
=3D
relationship between ADO.NET and XML, how and where to use ADO.NET in 
=3D
your enterprise applications, and how to use Web Services and ADO.NET to 
=3D
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm
---
Change your mail options at http://p2p.wrox.com/manager.asp or=3D20
to unsubscribe send a blank email to =3D
=3D=3D=3D
Fast Track ADO.NET with C# is a concise introduction to the concepts, 
techniques, and libraries that you will need in order to start using 
ADO.NET in your applications. The book covers DataSets and Typed 
DataSets, accessing data using DataReaders and DataAdaptors, the close 
relationship between ADO.NET and XML, how and where to use ADO.NET in 
your enterprise applications, and how to use Web Services and ADO.NET to 
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm

Message #5 by "h@f... on Thu, 20 Feb 2003 20:28:11 -0800 (PST)

Mind it dear, SqlDataReader or OledbDataReader is Forward Only, Read Only Object. U can' t use it for updation purpose. For that
purpose, use SqlDataAdapter with DataSet object.
Hafiz Qasim 
Punjab University, Lahore (Pakistan)
 marc cardenas <marclena@h...> wrote:Hi,
I am using a datareader to read a couple of records.
Then I'm trying to insert something on the database with the command 
object using the same connection than the datareader and I get an error 
message saying that I cannot use it because is a datareader open for that 
connection.
Cannot I have different datareaders pointing to the same connection.
Thanks
===
Fast Track ADO.NET with C# is a concise introduction to the concepts, techniques, and libraries that you will need in order to start
using ADO.NET in your applications. The book covers DataSets and Typed DataSets, accessing data using DataReaders and DataAdaptors,
the close relationship between ADO.NET and XML, how and where to use ADO.NET in your enterprise applications, and how to use Web
Services and ADO.NET to easily pass data between applications.
http://www.wrox.com/books/1861007604.htm


---------------------------------
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, and more

Message #6 by "Alex Smotritsky" <alex.smotritsky@v...> on Fri, 21 Feb 2003 06:37:24 -0500

You can use a datareader to update the database buy executing sql or a
stored procedure.

-----Original Message-----
From: h@f... [mailto:hafizqasim@y...] 
Sent: Thursday, February 20, 2003 11:28 PM
To: ADO.NET
Subject: [ado_dotnet] Re: DataReader

Mind it dear, SqlDataReader or OledbDataReader is Forward Only, Read
Only Object. U can' t use it for updation purpose. For that purpose, use
SqlDataAdapter with DataSet object. Hafiz Qasim 
Punjab University, Lahore (Pakistan)
 marc cardenas <marclena@h...> wrote:Hi,
I am using a datareader to read a couple of records.
Then I'm trying to insert something on the database with the command 
object using the same connection than the datareader and I get an error 
message saying that I cannot use it because is a datareader open for
that 
connection.
Cannot I have different datareaders pointing to the same connection.
Thanks === Fast Track ADO.NET with C# is a concise introduction to the
concepts, techniques, and libraries that you will need in order to start
using ADO.NET in your applications. The book covers DataSets and Typed
DataSets, accessing data using DataReaders and DataAdaptors, the close
relationship between ADO.NET and XML, how and where to use ADO.NET in
your enterprise applications, and how to use Web Services and ADO.NET to
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm

---------------------------------
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, and more

===
Fast Track ADO.NET with C# is a concise introduction to the concepts,
techniques, and libraries that you will need in order to start using
ADO.NET in your applications. The book covers DataSets and Typed
DataSets, accessing data using DataReaders and DataAdaptors, the close
relationship between ADO.NET and XML, how and where to use ADO.NET in
your enterprise applications, and how to use Web Services and ADO.NET to
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm

Message #7 by "Mike" <pcmike@u...> on Fri, 21 Feb 2003 09:34:12 -0500

Remember to explicitly close connections used by your DataReader, so
that you can reuse your connection for any other ADO.NET object that you
wish to instantiate.  I also explicitly close the connection when using
the connection object.  I've read several articles in MSDN that it is a
good habit to close connection explicitly.  See code below that I've use
to insert using the command object.

Note:  The DataAdapter Object works very well with the Connection
object.  It will implicitly control the opening and closing of a
connection for you.

Private Sub DataInsert()
        Dim ocmd As OleDbCommand
        Dim sSQL As String
        Dim intRows As Integer

        sSQL = "INSERT INTO Patient (LN, FN, FullName, DOB , SSN) "
        sSQL &= "VALUES ("
        sSQL &= Str2Field(txtLN.Text) & ", "
        sSQL &= Str2Field(txtFN.Text) & ", "
        sSQL &= Str2Field(txtFullName.Text) & ", "
        sSQL &= Str2Field(txtDOB.Text) & ","
        sSQL &= Str2Field(txtSSN.Text) & ")"

        Try
            ocmd = New OleDbCommand()
            With ocmd
                .Connection = New _
                    OleDbConnection(ConnectStringBuild())
                .Connection.Open()
                .CommandText = sSQL
                intRows = .ExecuteNonQuery()
                If intRows <> 1 Then
                    MessageBox.Show("Did not Insert row")
                    txtLN.Focus()
                    txtLN.Select()
                    Exit Sub
                Else
                    MessageBox.Show("Patient was successfully Added!!")

                    btnInsert.Enabled = False

                    txtSearch.Text = txtLN.Text
                    lstPatient.Items.Clear()

                    txtPID.Text = ""
                    txtLN.Text = ""
                    txtFN.Text = ""
                    txtFullName.Text = ""
                    txtDOB.Text = ""
                    txtSSN.Text = ""

                    btnSearch.Focus()

                End If
                .Connection.Close()
            End With

        Catch oException As Exception
            MessageBox.Show(oException.Message)

        End Try

    End Sub


Mike


-----Original Message-----
From: Alex Smotritsky [mailto:alex.smotritsky@v...] 
Sent: Friday, February 21, 2003 6:37 AM
To: ADO.NET
Subject: [ado_dotnet] Re: DataReader

You can use a datareader to update the database buy executing sql or a
stored procedure.


-----Original Message-----
From: h@f... [mailto:hafizqasim@y...] 
Sent: Thursday, February 20, 2003 11:28 PM
To: ADO.NET
Subject: [ado_dotnet] Re: DataReader



Mind it dear, SqlDataReader or OledbDataReader is Forward Only, Read
Only Object. U can' t use it for updation purpose. For that purpose, use
SqlDataAdapter with DataSet object. Hafiz Qasim 
Punjab University, Lahore (Pakistan)
 marc cardenas <marclena@h...> wrote:Hi,
I am using a datareader to read a couple of records.
Then I'm trying to insert something on the database with the command 
object using the same connection than the datareader and I get an error 
message saying that I cannot use it because is a datareader open for
that 
connection.
Cannot I have different datareaders pointing to the same connection.
Thanks === Fast Track ADO.NET with C# is a concise introduction to the
concepts, techniques, and libraries that you will need in order to start
using ADO.NET in your applications. The book covers DataSets and Typed
DataSets, accessing data using DataReaders and DataAdaptors, the close
relationship between ADO.NET and XML, how and where to use ADO.NET in
your enterprise applications, and how to use Web Services and ADO.NET to
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm


---------------------------------
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, and more

===
Fast Track ADO.NET with C# is a concise introduction to the concepts,
techniques, and libraries that you will need in order to start using
ADO.NET in your applications. The book covers DataSets and Typed
DataSets, accessing data using DataReaders and DataAdaptors, the close
relationship between ADO.NET and XML, how and where to use ADO.NET in
your enterprise applications, and how to use Web Services and ADO.NET to
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm


===
Fast Track ADO.NET with C# is a concise introduction to the concepts,
techniques, and libraries that you will need in order to start using
ADO.NET in your applications. The book covers DataSets and Typed
DataSets, accessing data using DataReaders and DataAdaptors, the close
relationship between ADO.NET and XML, how and where to use ADO.NET in
your enterprise applications, and how to use Web Services and ADO.NET to
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm

Message #8 by "Duncan" <duncan.faulkner1@b...> on Fri, 21 Feb 2003 15:13:44 -0000

Hi

An alternative to explicitly closing the connection is to pass
CommandBehaviour.CloseConnection to the ExecuteReader method to ensure
that the associated connection is closed when the datareader is closed.
This is useful if you are returning a datareader from a method and you
do not have control over closing of the datareader or associated
connection.

Duncan

-->-----Original Message-----
-->From: Mike [mailto:pcmike@u...] 
-->Sent: 21 February 2003 14:34
-->To: ADO.NET
-->Subject: [ado_dotnet] Re: DataReader
-->
-->
-->Remember to explicitly close connections used by your 
-->DataReader, so that you can reuse your connection for any 
-->other ADO.NET object that you wish to instantiate.  I also 
-->explicitly close the connection when using the connection 
-->object.  I've read several articles in MSDN that it is a 
-->good habit to close connection explicitly.  See code below 
-->that I've use to insert using the command object.
-->
-->Note:  The DataAdapter Object works very well with the 
-->Connection object.  It will implicitly control the opening 
-->and closing of a connection for you.
-->
-->Private Sub DataInsert()
-->        Dim ocmd As OleDbCommand
-->        Dim sSQL As String
-->        Dim intRows As Integer
-->
-->        sSQL = "INSERT INTO Patient (LN, FN, FullName, DOB , SSN) "
-->        sSQL &= "VALUES ("
-->        sSQL &= Str2Field(txtLN.Text) & ", "
-->        sSQL &= Str2Field(txtFN.Text) & ", "
-->        sSQL &= Str2Field(txtFullName.Text) & ", "
-->        sSQL &= Str2Field(txtDOB.Text) & ","
-->        sSQL &= Str2Field(txtSSN.Text) & ")"
-->
-->        Try
-->            ocmd = New OleDbCommand()
-->            With ocmd
-->                .Connection = New _
-->                    OleDbConnection(ConnectStringBuild())
-->                .Connection.Open()
-->                .CommandText = sSQL
-->                intRows = .ExecuteNonQuery()
-->                If intRows <> 1 Then
-->                    MessageBox.Show("Did not Insert row")
-->                    txtLN.Focus()
-->                    txtLN.Select()
-->                    Exit Sub
-->                Else
-->                    MessageBox.Show("Patient was 
-->successfully Added!!")
-->
-->                    btnInsert.Enabled = False
-->
-->                    txtSearch.Text = txtLN.Text
-->                    lstPatient.Items.Clear()
-->
-->                    txtPID.Text = ""
-->                    txtLN.Text = ""
-->                    txtFN.Text = ""
-->                    txtFullName.Text = ""
-->                    txtDOB.Text = ""
-->                    txtSSN.Text = ""
-->
-->                    btnSearch.Focus()
-->
-->                End If
-->                .Connection.Close()
-->            End With
-->
-->        Catch oException As Exception
-->            MessageBox.Show(oException.Message)
-->
-->        End Try
-->
-->    End Sub
-->
-->
-->Mike
-->
-->
-->-----Original Message-----
-->From: Alex Smotritsky [mailto:alex.smotritsky@v...] 
-->Sent: Friday, February 21, 2003 6:37 AM
-->To: ADO.NET
-->Subject: [ado_dotnet] Re: DataReader
-->
-->You can use a datareader to update the database buy 
-->executing sql or a stored procedure.
-->
-->
-->-----Original Message-----
-->From: h@f... [mailto:hafizqasim@y...] 
-->Sent: Thursday, February 20, 2003 11:28 PM
-->To: ADO.NET
-->Subject: [ado_dotnet] Re: DataReader
-->
-->
-->
-->Mind it dear, SqlDataReader or OledbDataReader is Forward 
-->Only, Read Only Object. U can' t use it for updation 
-->purpose. For that purpose, use SqlDataAdapter with DataSet 
-->object. Hafiz Qasim 
-->Punjab University, Lahore (Pakistan)
--> marc cardenas <marclena@h...> wrote:Hi,
-->I am using a datareader to read a couple of records.
-->Then I'm trying to insert something on the database with the command 
-->object using the same connection than the datareader and I 
-->get an error 
-->message saying that I cannot use it because is a datareader 
-->open for that 
-->connection.
-->Cannot I have different datareaders pointing to the same 
-->connection. Thanks === Fast Track ADO.NET with C# is a 
-->concise introduction to the concepts, techniques, and 
-->libraries that you will need in order to start using ADO.NET 
-->in your applications. The book covers DataSets and Typed 
-->DataSets, accessing data using DataReaders and DataAdaptors, 
-->the close relationship between ADO.NET and XML, how and 
-->where to use ADO.NET in your enterprise applications, and 
-->how to use Web Services and ADO.NET to easily pass data 
-->between applications. http://www.wrox.com/books/1861007604.htm
-->---
-->
-->
-->
-->
-->---------------------------------
-->Do you Yahoo!?
-->Yahoo! Tax Center - forms, calculators, tips, and more
-->
-->===
-->Fast Track ADO.NET with C# is a concise introduction to the 
-->concepts, techniques, and libraries that you will need in 
-->order to start using ADO.NET in your applications. The book 
-->covers DataSets and Typed DataSets, accessing data using 
-->DataReaders and DataAdaptors, the close relationship between 
-->ADO.NET and XML, how and where to use ADO.NET in your 
-->enterprise applications, and how to use Web Services and 
-->ADO.NET to easily pass data between applications. 
-->http://www.wrox.com/books/1861007604.htm
-->---
-->Change your 
-->mail options at 
-->
-->
-->
-->
-->===
-->Fast Track ADO.NET with C# is a concise introduction to the 
-->concepts, techniques, and libraries that you will need in 
-->order to start using ADO.NET in your applications. The book 
-->covers DataSets and Typed DataSets, accessing data using 
-->DataReaders and DataAdaptors, the close relationship between 
-->ADO.NET and XML, how and where to use ADO.NET in your 
-->enterprise applications, and how to use Web Services and 
-->ADO.NET to easily pass data between applications. 
-->http://www.wrox.com/books/1861007604.htm
-->---
-->Change your 
-->mail options at 
-->
-->
-->
-->
-->===
-->Fast Track ADO.NET with C# is a concise introduction to the 
-->concepts, techniques, and libraries that you will need in 
-->order to start using ADO.NET in your applications. The book 
-->covers DataSets and Typed DataSets, accessing data using 
-->DataReaders and DataAdaptors, the close relationship between 
-->ADO.NET and XML, how and where to use ADO.NET in your 
-->enterprise applications, and how to use Web Services and 
-->ADO.NET to easily pass data between applications. 
-->http://www.wrox.com/books/1861007604.htm
-->---
-->Change your 
-->mail options at 
-->
-->
-->

Message #9 by "Mike" <pcmike@u...> on Fri, 21 Feb 2003 10:44:52 -0500

Thanks for the reminder about CommandBhavior.  I remember using this as
well.

Example of its use:

           Dim ocmd As OleDbCommand
           Dim odr As OleDataReader
-->        Dim sSQL As String
-->        Dim intRows As Integer
-->
-->        sSQL = "INSERT INTO Patient (LN, FN, FullName, DOB , SSN) "
-->        sSQL &= "VALUES ("
-->        sSQL &= Str2Field(txtLN.Text) & ", "
-->        sSQL &= Str2Field(txtFN.Text) & ", "
-->        sSQL &= Str2Field(txtFullName.Text) & ", "
-->        sSQL &= Str2Field(txtDOB.Text) & ","
-->        sSQL &= Str2Field(txtSSN.Text) & ")"
-->
-->        Try
-->            ocmd = New OleDbCommand()
-->            With ocmd
-->                .Connection = New _
-->                    OleDbConnection(ConnectStringBuild())
-->                .Connection.Open()
-->                .CommandText = sSQL

-->                'Closes connection when closing DataReader object
                   odr = .ExecuteReader(CommandBehavior.CloseConnection)
               End With


Mike


-----Original Message-----
From: Duncan [mailto:duncan.faulkner1@b...] 
Sent: Friday, February 21, 2003 10:14 AM
To: ADO.NET
Subject: [ado_dotnet] Re: DataReader

Hi

An alternative to explicitly closing the connection is to pass
CommandBehaviour.CloseConnection to the ExecuteReader method to ensure
that the associated connection is closed when the datareader is closed.
This is useful if you are returning a datareader from a method and you
do not have control over closing of the datareader or associated
connection.

Duncan

-->-----Original Message-----
-->From: Mike [mailto:pcmike@u...] 
-->Sent: 21 February 2003 14:34
-->To: ADO.NET
-->Subject: [ado_dotnet] Re: DataReader
-->
-->
-->Remember to explicitly close connections used by your 
-->DataReader, so that you can reuse your connection for any 
-->other ADO.NET object that you wish to instantiate.  I also 
-->explicitly close the connection when using the connection 
-->object.  I've read several articles in MSDN that it is a 
-->good habit to close connection explicitly.  See code below 
-->that I've use to insert using the command object.
-->
-->Note:  The DataAdapter Object works very well with the 
-->Connection object.  It will implicitly control the opening 
-->and closing of a connection for you.
-->
-->Private Sub DataInsert()
-->        Dim ocmd As OleDbCommand
-->        Dim sSQL As String
-->        Dim intRows As Integer
-->
-->        sSQL = "INSERT INTO Patient (LN, FN, FullName, DOB , SSN) "
-->        sSQL &= "VALUES ("
-->        sSQL &= Str2Field(txtLN.Text) & ", "
-->        sSQL &= Str2Field(txtFN.Text) & ", "
-->        sSQL &= Str2Field(txtFullName.Text) & ", "
-->        sSQL &= Str2Field(txtDOB.Text) & ","
-->        sSQL &= Str2Field(txtSSN.Text) & ")"
-->
-->        Try
-->            ocmd = New OleDbCommand()
-->            With ocmd
-->                .Connection = New _
-->                    OleDbConnection(ConnectStringBuild())
-->                .Connection.Open()
-->                .CommandText = sSQL
-->                intRows = .ExecuteNonQuery()
-->                If intRows <> 1 Then
-->                    MessageBox.Show("Did not Insert row")
-->                    txtLN.Focus()
-->                    txtLN.Select()
-->                    Exit Sub
-->                Else
-->                    MessageBox.Show("Patient was 
-->successfully Added!!")
-->
-->                    btnInsert.Enabled = False
-->
-->                    txtSearch.Text = txtLN.Text
-->                    lstPatient.Items.Clear()
-->
-->                    txtPID.Text = ""
-->                    txtLN.Text = ""
-->                    txtFN.Text = ""
-->                    txtFullName.Text = ""
-->                    txtDOB.Text = ""
-->                    txtSSN.Text = ""
-->
-->                    btnSearch.Focus()
-->
-->                End If
-->                .Connection.Close()
-->            End With
-->
-->        Catch oException As Exception
-->            MessageBox.Show(oException.Message)
-->
-->        End Try
-->
-->    End Sub
-->
-->
-->Mike
-->
-->
-->-----Original Message-----
-->From: Alex Smotritsky [mailto:alex.smotritsky@v...] 
-->Sent: Friday, February 21, 2003 6:37 AM
-->To: ADO.NET
-->Subject: [ado_dotnet] Re: DataReader
-->
-->You can use a datareader to update the database buy 
-->executing sql or a stored procedure.
-->
-->
-->-----Original Message-----
-->From: h@f... [mailto:hafizqasim@y...] 
-->Sent: Thursday, February 20, 2003 11:28 PM
-->To: ADO.NET
-->Subject: [ado_dotnet] Re: DataReader
-->
-->
-->
-->Mind it dear, SqlDataReader or OledbDataReader is Forward 
-->Only, Read Only Object. U can' t use it for updation 
-->purpose. For that purpose, use SqlDataAdapter with DataSet 
-->object. Hafiz Qasim 
-->Punjab University, Lahore (Pakistan)
--> marc cardenas <marclena@h...> wrote:Hi,
-->I am using a datareader to read a couple of records.
-->Then I'm trying to insert something on the database with the command 
-->object using the same connection than the datareader and I 
-->get an error 
-->message saying that I cannot use it because is a datareader 
-->open for that 
-->connection.
-->Cannot I have different datareaders pointing to the same 
-->connection. Thanks === Fast Track ADO.NET with C# is a 
-->concise introduction to the concepts, techniques, and 
-->libraries that you will need in order to start using ADO.NET 
-->in your applications. The book covers DataSets and Typed 
-->DataSets, accessing data using DataReaders and DataAdaptors, 
-->the close relationship between ADO.NET and XML, how and 
-->where to use ADO.NET in your enterprise applications, and 
-->how to use Web Services and ADO.NET to easily pass data 
-->between applications. http://www.wrox.com/books/1861007604.htm
-->---
-->
-->
-->
-->
-->---------------------------------
-->Do you Yahoo!?
-->Yahoo! Tax Center - forms, calculators, tips, and more
-->
-->===
-->Fast Track ADO.NET with C# is a concise introduction to the 
-->concepts, techniques, and libraries that you will need in 
-->order to start using ADO.NET in your applications. The book 
-->covers DataSets and Typed DataSets, accessing data using 
-->DataReaders and DataAdaptors, the close relationship between 
-->ADO.NET and XML, how and where to use ADO.NET in your 
-->enterprise applications, and how to use Web Services and 
-->ADO.NET to easily pass data between applications. 
-->http://www.wrox.com/books/1861007604.htm
-->---
-->Change your 
-->mail options at 
-->
-->
-->
-->
-->===
-->Fast Track ADO.NET with C# is a concise introduction to the 
-->concepts, techniques, and libraries that you will need in 
-->order to start using ADO.NET in your applications. The book 
-->covers DataSets and Typed DataSets, accessing data using 
-->DataReaders and DataAdaptors, the close relationship between 
-->ADO.NET and XML, how and where to use ADO.NET in your 
-->enterprise applications, and how to use Web Services and 
-->ADO.NET to easily pass data between applications. 
-->http://www.wrox.com/books/1861007604.htm
-->---
-->Change your 
-->mail options at 
-->
-->
-->
-->
-->===
-->Fast Track ADO.NET with C# is a concise introduction to the 
-->concepts, techniques, and libraries that you will need in 
-->order to start using ADO.NET in your applications. The book 
-->covers DataSets and Typed DataSets, accessing data using 
-->DataReaders and DataAdaptors, the close relationship between 
-->ADO.NET and XML, how and where to use ADO.NET in your 
-->enterprise applications, and how to use Web Services and 
-->ADO.NET to easily pass data between applications. 
-->http://www.wrox.com/books/1861007604.htm
-->---
-->Change your 
-->mail options at 
-->
-->
-->


===
Fast Track ADO.NET with C# is a concise introduction to the concepts,
techniques, and libraries that you will need in order to start using
ADO.NET in your applications. The book covers DataSets and Typed
DataSets, accessing data using DataReaders and DataAdaptors, the close
relationship between ADO.NET and XML, how and where to use ADO.NET in
your enterprise applications, and how to use Web Services and ADO.NET to
easily pass data between applications.
http://www.wrox.com/books/1861007604.htm

Return to Index

P2P Archives