Sams Teach Yourself ASP.NET in 21 Days, Second Edition By Chris Payne
Table of Contents
Day 10. Communicating with ADO.NET
This workshop will help reinforce the concepts covered in today's lesson. The answers can be found in Appendix A.
Quiz
1:
What are the two major parts of ADO.NET?
2:
What do managed providers do?
3:
What is disconnected data?
4:
Which of the following constructors isn't valid for the OleDbCommand object (line 4, 5, 6, 8, or 9)?
dim strSQL as string = "SELECT * FROM tblUsers") dim Conn as new OleDbConnection("DSN=21DaysBanking") dim objCmd as new OleDbCommand() dim objCmd as new OleDbCommand(strSQL) dim objCmd as new OleDbCommand(strSQL, _Conn) dim objCmd as new OleDbCommand(Conn) dim objCmd as new OleDbCommand(strSQL, _ "DSN=21DaysBanking")
5:
What type of data model does an OleDbCommand object fill?
6:
Does an OleDbCommand object need to be closed?
7:
What are the five members of the OleDbDataAdapter object?
8:
Which of the following constructors isn't valid for the OleDbDataAdapter object (line 5, 6, 7, 9, or 10)?
dim strSQL as string = "SELECT * FROM tblUsers") dim Conn as new OleDbConnection("DSN=21DaysBanking") dim objADOCmd as new OleDbCommand(strSQL, Conn) dim objCmd as new OleDbDataAdapter() dim objCmd as new OleDbDataAdapter(objADOCmd) dim objCmd as new OleDbDataAdapter(strSQL, _ Conn) dim objCmd as new OleDbDataAdapter(Conn) dim objCmd as new OleDbDataAdapter(strSQL, _ "DSN=21DaysBanking")
Exercises
[click here]
Modify the example application you built today to use the OleDbDataAdapter and DataSet objects instead of OleDbCommand and OleDbDataReader. If you use the OleDbCommandBuilder as well, don't forget the limitation about the initial select statement matching the columns in the DataSet that was described earlier today.
