• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Part IV: Upsizing > From DAO to ADO

Chapter 17. From DAO to ADO

If you need to convert Data Access Objects (DAO) programs to Microsoft ActiveX Data Objects (ADO), or if you are familiar with DAO, you might find the descriptions and listings presented in this chapter helpful. They compare DAO commands and ADO commands.

Many DAO commands do not have corresponding commands in ADO. In some cases, DAO commands are no longer needed or no longer functional due to the new structures of Access projects. Specifically, you cannot convert any commands for creating tables and queries, as ADO does not have corresponding commands for these functions. With mdb databases based on Jet Engine, you can also use the routines in the Microsoft ADO Extensions for Data Definition and Security (ADOX) library to create tables and queries. However, ADOX has primarily read-only support with the Microsoft SQL Server OLE DB provider, and many of the methods are not supported. The same applies to the DAO replication commands, which are available for Jet Engine ADO programming in the Microsoft Jet and Replication Objects (JRO) library. This library also cannot be used with SQL Server/MSDE. SQL Server/MSDE exposes most of the functionality of ADOX and JRO directly through systems stored procedures and the SQL Distributed Management Objects (SQL-DMO) library, covered in Chapter 25, “System Stored Procedures,” and Chapter 23, “The SQL-DMO Library,” respectively.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint