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.
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.
--
____________________________________)
-----------------------------------------------------------------------------------------------------------------------
"Garry" <garrygrolman@xxxxxxxxx> wrote in message
news:%23SURfWtCHHA.4928@xxxxxxxxxxxxxxxxxxxxxxx: Garry
- References:
- MS Access DAO -> ADO.NET Migration
- From: moomoofatcow
- Re: MS Access DAO -> ADO.NET Migration
- From: Garry
- 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):