Help with example (MS Access)

[some-1]

Hi All,
I am sure the topics in this forum has an answer somewhere to my question. My question is divided into two parts, regarding connecting my VB.NET application to MS Access mdb file:

Part 1: I already have the code working to access and mdb file using ADODB.Connection. I can loop through the records in MS Access tables and everyhing is fine. Now I read the topics in this forum and I understand that it seems that in VB.NET I should use Microsoft.Jet.OLEDB.4.0 to connect to my mdb file? Why? Which one is faster and especially that I am looping through tables conatining 100s of rows?

Part 2: I tried despiratly to find a start-up VB.NET code example bu failed. Where can I find it? Many of the users in this forum posts code specific to a purpose. I will really appreciate your support in this.

Thank you all

 

[ajeeshco]

Check these articles http://visualbasic.about.com/od/learnvbnetandadonet/l/aa050303a.htm, http://www.startvbdotnet.com/ado/msaccess.aspx

 

[AtomCom2001]

I wish there was a site the easily explain all about Data Connecters etc for different data sources.

ie

for access97
....OLEDB
........Advantages / disadvantages
........Example
....ADO.net
........Advantages / disadvantages
........Example

Maybe there is already a site that does this.. ?

by the way I know www.connectionstrings.com is a very good site to start with.. though does not really explain why and where you should use the different types

 

[some-1]

Thanks guys for the useful information. They will help me a lot.

The www.connectionstrings.com page is really useful.

 

[cjard]

Hi All,
I am sure the topics in this forum has an answer somewhere to my question. My question is divided into two parts, regarding connecting my VB.NET application to MS Access mdb file:

Part 1: I already have the code working to access and mdb file using ADODB.Connection. I can loop through the records in MS Access tables and everyhing is fine. Now I read the topics in this forum and I understand that it seems that in VB.NET I should use Microsoft.Jet.OLEDB.4.0 to connect to my mdb file? Why? Which one is faster and especially that I am looping through tables conatining 100s of rows?

I think you might find that ADODB.Connection is a suite of objects intended for legacy apps (i.e. its an old, back compatibility presence), while Microsoft.Jet.OLEDB.4.0 is a database driver (data provider). i.e. they are different things, and necessarily ADODB.Connection uses Microsoft.Jet.OLEDB.4.0 to conenct to an access datasource.

What you really ought to be asking, is how to use ADO.NET to access an Access (Jet) database, and that would be a question for the ADO.NET section of the forum

Part 2: I tried despiratly to find a start-up VB.NET code example bu failed. Where can I find it? Many of the users in this forum posts code specific to a purpose. I will really appreciate your support in this.

Read the DW2 link in my signature, section on "Creating a Simple Data App"

 

[cjard]

I wish there was a site the easily explain all about Data Connecters etc for different data sources.

ie

for access97
....OLEDB
........Advantages / disadvantages
........Example
....ADO.net
........Advantages / disadvantages
........Example

OleDb (Microsoft.Jet.OLEDB.4.0) is a provider used by ADO.NET. Given that ADO.NET (can) uses it to operate, it isnt a case of using one or the other - its a case of one using the other. As an analogy, in the same way that Audi, Volkswagen and Ford (ADO.NET) all use the VAG 2.8 V6 engine (OleDb) in their cars. They are, additionally, free to use other engines (data providers) for other purposes.

You need to look at the ADO.NET diagram that came with your boxed copy of Visual Studio. If you have an.. er.. electronic copy, that could be why youre a bit nonplussed..

ADO.NET can use any data provider to connect to any data source. I.e. it uses Oracle, SQLServer and Jet natively to connect to the relevant databases. It can also use Odbc, and in turn Odbc drivers exist for various databases. This adds a level of indirection, reducing feature set and performance.