Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Which one can be the better one data access component for desktop application and why?
1.) For MS Access 2007: ADO, OLEDB, DAO
2.) For MSSQL 2005: ADO, OLEDB, DAO
DAO is hopelessly antiquated, it doesn’t support the engines you listed. OLEDB and ADO are complementary, OLEDB provides the dbase engine interface, ADO is a grab bag of the classes you’ll use in your code to program the dbase interface. ADO.NET in the .NET framework.
For Access you’d use the classes in the System.Data.OleDb namespace, your connection string uses the ACE provider. For SQL you’d best use the classes in the System.Data.SqlClient namespace. Visit connectionstrings.com for help with configuring the connection strings.