Re: MS Access DAO -> ADO.NET Migration
- From: "William \(Bill\) Vaughn" <billvaRemoveThis@xxxxxxxxxx>
- Date: Fri, 17 Nov 2006 13:52:00 -0800
This is an oft-discussed topic so be sure to use Google groups to search the
archives. Remember that DAO is the JET DBMS (the data engine used by Access
by default) "native" data access interface. JET is an ISAM engine that gets
some of its performance by permitting access to the "TableDirect" IO scheme
that simply walks a developer-selected index--this approach is not usually
implemented in traditional relational DBMS engines. ADO.NET in contrast is
very different. The Framework exposes several .NET Data Providers that are
written specifically to work with the target DBMS. For example, if you're
using OLE DB (via the OleDb namespace) instead of DAO you've just added a
complex and bulky layer between you and the data. There are several
alternatives to JET today. Anyone converting from Access/VB6 should consider
another (more scalable, more secure engine). Yes, SQL Server is an
alternative but now that MS has released the Compact Edition, it can also
serve as a fast, light DBMS alternative that's fully encryptable. It
supports TableDirect as well as scrollable, updatable curors. Yes, the
Compact Edition is a single-user DBMS engine so if you're planning to create
a multiuser application, you'll need to look back to SQL Server Express or
other engines.
Again, DBMS choice is a big (fundamental) decision--that's why its covered
in detail in my new book.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
-----------------------------------------------------------------------------------------------------------------------
<moomoofatcow@xxxxxxxxxxx> wrote in message
news:1163796070.268114.323610@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have an VB6 program that I wrote that access Microsoft Access
databases using DAO. DAO has methods and properties that are Access
specific (such as viewing and editing relationships or indexes on the
tables) I want to write a new version of the program in VB 2005, and I
want to use ADO.NET to access the data. Are there ways of changing the
indexes or relationships of the MS Access database using ADO.NET? Or do
I still need to use DAO to perform these operations?
As a side note, with a few tests that I've done already with some
queries, it seems like DAO is much faster than ADO.NET at running
queries and returning results. I am using the DataReader...does anyone
have any information about the differences etc? Thanks in advance...
.
- References:
- MS Access DAO -> ADO.NET Migration
- From: moomoofatcow
- MS Access DAO -> ADO.NET Migration
- Prev by Date: Re: please help! Error in update Access database
- Next by Date: Migrating from MS ACCESS 97 to SSEv
- Previous by thread: MS Access DAO -> ADO.NET Migration
- Next by thread: Re: MS Access DAO -> ADO.NET Migration
- Index(es):
Relevant Pages
|
Loading
