Re: MS Access DAO -> ADO.NET Migration
- From: "William \(Bill\) Vaughn" <billvaRemoveThis@xxxxxxxxxx>
- Date: Sat, 18 Nov 2006 10:14:55 -0800
I also share your frustration with the Microsoft doc. You'll also find that
Intellisense does not help either. That's because it leads you to think that
specific types, methods, properties and events are exposed when they are
not--you won't find out until runtime. To deal with this issue, I wrote my
first EBook that walks through the entire namespace and documents how it
really works. It's written for developers that are somewhat familiar with
the SqlClient namespace and ADO.NET in general (and those that have read my
Hitchhiker's Guide to Visual Studio and SQL Server book. This book is
available at http://www.hitchhikerguides.net/EBooks/Titles/5582.aspx.
Incidentally, Microsoft chose to change the name from SQL Server Everywhere
Edition to SQL Server 2005 Compact Edition about three weeks ago. This
version of the SQLCe DBMS engine has been tuned to run in a Windows Forms
environment. It's a fully relational database that supports a subset of the
TSQL SQL syntax. It's easy to deploy (just copy 6 DLLs), is fully
encryptable (so it's safer for data you take to the field) and has twice the
capacity of JET (4GB). SQLCe is also designed to act as a Subscriber to a
SQL Server-hosted Publication. This can make it even easier to construct a
distributed architecture around SQLCe. MS is still doing work on the Visual
Studio and SQL Server Enterprise Manager development tools but the EBook
shows how to get around these limitations until the next SP or Orcas ships.
Early next year, I'll be publishing the next in my series of EBooks. This
time on SQLCe Replication. I'm waiting for MS to finish work on a new
replication scheme that promises to be easier to use than their current
approaches.
--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------
"Garry" <garrygrolman@xxxxxxxxx> wrote in message
news:%23SURfWtCHHA.4928@xxxxxxxxxxxxxxxxxxxxxxx
I had your problem basically and am working at the moment to transfer
existing Access 97 databases, (with data), to SQL Server Everywhere, the
new/old database referred to by William (Bill) Vaughn. He suggested to me
that I use this new database for .NET 2005 development where the DataBase
requirements are similar to what I had in a VB6/Access97 desktop
application.
I am working on an app to migrate the Access 97 database to the SSEv
database and it is going relatively smoothly. Although, there are some
problems as I have defined in a post a little above yours.
I do not expect to edit relationships within the predefined database OR
re-define existing tables BUT, I have seen reference to code which can do
this.
If you try to find code samples - do yourself a favor, use Google as
William (Bill) Vaughn valiantly suggests. Microsoft help is, in many
cases, gibberish, which will not solve your query and will just make you
angry and frustrated. I wonder when Microsoft will catch on a construct a
serious library of code samples instead of the meager offerings available.
If any of the Google search results take you to forums which require that
you 'join', be careful. Some of these forums even want you to pay to join
without you knowing if a solution is actually available there.
Be careful about using Sponsored Links as these must have some financial
incentives involved otherwise they would not be there. It costs money to
put a Sponsored Link on a Google Search result page. Every click means
that money is earned by Google.
If you want to go down this route, use 'Reply to Sender' as well as 'Reply
to group' and I will send you my code which is a near completed
application in VB.NET. I do not want to post my email address here.
I need an exchange of info and opinions from another programmer who is
having similar, if not identical problems.
Garry
<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...
.
- Follow-Ups:
- Re: MS Access DAO -> ADO.NET Migration
- From: Garry
- Re: MS Access DAO -> ADO.NET Migration
- References:
- MS Access DAO -> ADO.NET Migration
- From: moomoofatcow
- Re: MS Access DAO -> ADO.NET Migration
- From: Garry
- MS Access DAO -> ADO.NET Migration
- Prev by Date: Re: Beginning question for Access OLEDBUpdate command
- Next by Date: Re: More advanced examples for the impatient "newby"
- Previous by thread: Re: MS Access DAO -> ADO.NET Migration
- Next by thread: Re: MS Access DAO -> ADO.NET Migration
- Index(es):
Relevant Pages
|
