So Many ADO Data Providers Which Should I Use?
-
I am coming from VB6. I looked up NET database examples for MS Access and find there are several ways to do the same thing. I saw one example use a OleDb provider, one used a ADO provider, and one used a SqlClient. My quesiton is- what should i be learning? Which should i use? What do most programmers use? My program philosophy is KISS. I think OleDb provides generic access? But i am not sure. Some advice from experienced programmers would be helpful.
-
I am coming from VB6. I looked up NET database examples for MS Access and find there are several ways to do the same thing. I saw one example use a OleDb provider, one used a ADO provider, and one used a SqlClient. My quesiton is- what should i be learning? Which should i use? What do most programmers use? My program philosophy is KISS. I think OleDb provides generic access? But i am not sure. Some advice from experienced programmers would be helpful.
Hello Depending on which database you are building you should choose the data provider. The data provider actually is nothing but a mediator between the real DBMS and you .Net code. So if you are using/accessing an Access DB then OLEDb is best for you. OTOH if you want to make SQL server database for sure you'd use SQLDb provider. for Oracle and other ODBC engines ODBC provider is intuitively your choice. Was that what you were asking for? And what is KISS BTW?
Regards:rose:
-
Hello Depending on which database you are building you should choose the data provider. The data provider actually is nothing but a mediator between the real DBMS and you .Net code. So if you are using/accessing an Access DB then OLEDb is best for you. OTOH if you want to make SQL server database for sure you'd use SQLDb provider. for Oracle and other ODBC engines ODBC provider is intuitively your choice. Was that what you were asking for? And what is KISS BTW?
Regards:rose:
Sorry, i forgot about all the non-english speakers on this forum. KISS stands for Keep It Simple. I am not a programmer who always reaches for the latest technology to solve a problem because often the technologies are not mature and have many undocumented problems. I learned that ADO from VB6 is supported in NET for backward compatibility. That was confusing me. I now understand that OleDb is the choice to use for NET.