Explain the relationships among native DBMS libraries, ODBC, OLE ...

[Pineappleeh]

Explain the relationships among native DBMS libraries, ODBC, OLE DB, ADO, and ADO.NET and why each led to the development of the next.
 
  What will be an ideal response?

Question 2

Which of the following statements about Subtype objects is not true?
 
  A) Subtypes can be Inclusive (an object may be more than one subtype).
  B) Subtypes can be Exclusive (an object may only be one of the subtypes).
  C) Subtypes can be Nested.
  D) All relations between the parent and subtype are 1:N.

[af]

Answer to Question 1

All of these provide means of data access. Native DBMS libraries are the least abstract and are DBMS-specific access methods. Due to the large numbers of data sources that developers have to deal with, learning that many DBMS libraries was cumbersome. ODBC developed as a more abstract means of data access that shielded developers from having to learn multiple native DBMS libraries. One shortcoming of ODBC, however, was that it can only access data from sources that have a table-like structure. Therefore, OLE DB was developed as a means of accessing data from a much broader range of data source types. OLE DB is an object-oriented interface that is suitable for use by many object-oriented languages. Many developers, however, use languages such as Visual Basic and scripting languages that cannot access OLE DB. ADO was therefore developed to further abstract OLE DB and provide access to OLE DB functionality to programming languages that cannot directly access OLE DB. ADO has been followed by ADO.NET, which is part of Microsoft's .NET initiative. It extends the functionality of ADO.

Answer to Question 2

D