Re: ADO to ADO.NET 2.0

Tech-Archive recommends: Speed Up your PC by fixing your registry

Nope, it's too long to do online and the profit motive is just not there. I
can come to your site to give a custom talk that includes the 2.0 changes as
well as bring you and your team up to speed on the conversion issues. The
2.0 book won't be out until AW finishes editing it.
See www.hitchhikerguides.net for current info.


--
____________________________________
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.
__________________________________

"steve" <noemail> wrote in message
news:eiAi5fAhGHA.4776@xxxxxxxxxxxxxxxxxxxxxxx
Bill,

Thanks for info. Unfortunately, I won't be attending VSLive. Any chance
of workshop appearing on-line?
Any idea when the 2.0 version of the book will be published? It looks
like it could be very helpful. And thanks for offering your help. When
we know more about what we don't know, I might take you up on your offer.
Contact you first via email?

Thanks again.

Steve

"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:epW9koQgGHA.3916@xxxxxxxxxxxxxxxxxxxxxxx
Steve, I'm giving a day-long workshop on ADO.NET 2.0 architectures and
best practices at the VSLive (Vegas) conference. I think this could go a
long way to answering your questions. In addition, my APress book ("ADO
and ADO.NET Examples and Best Practices") was designed specifically for
you. It walks through the issues faced by developers with the same
challenges--migrating from VB6 to VB.NET. While it does not discuss the
2.0 version of ADO.NET (that book is in edit), the core discussion will
help a lot and it's written with VB developers in mind. I would also be
happy to spend a few minutes on the phone to help get you started out on
the right foot. IMHO, it would be a mistake to stick with JET/Access at
this point in the technology. While JET can seem like an easy-to-use
engine, MS is doing whatever it can to back away from this dated engine.
SQL Express is far more mature (it's based on the SQL Server binaries
that have been around for a long time). It also might be overkill so I'm
encouraging developers to consider SQL Everywhere as a lightweight
alternative. I discuss all of these issues in my workshop.

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.
__________________________________

"steve" <noemail> wrote in message
news:Okps4cOgGHA.4864@xxxxxxxxxxxxxxxxxxxxxxx
David,

Thanks for the reply. We're too early in the process to know if we're
going to use SQL Express or Access or to know if and what relationships
will be defined in the db.

However, it's not clear to me why using multiple related tables in
ADO.NET datasets is better than binding to joined tables for updates.
Could you elaborate or steer me to a reference?

Steve

"David Browne" <davidbaxterbrowne no potted meat@xxxxxxxxxxx> wrote in
message news:eOzZ9dNgGHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
The good news is that in ADO.NET you don't have to use a JOIN to fetch,
bind and update data from multiple tables. The ADO.NET DataSet lets
you use multiple related tables. In general this much better than
binding to join tables.

However, you can use a JOIN in ADO.NET. The specifics depend on the
back-end. In SQL Server (Express) you would create a VIEW in the
database and use it just like a table. So long as your updates affect
only one base table, it all just works. If your updates target
multiple tables you can define INSTEAD OF triggers on the view to route
the changes to the appropriate base tables.


David










.

Relevant Pages

  • Re: ADO to ADO.NET 2.0
    ... It walks through the issues faced by developers with the same ... SQL Express is far more mature (it's based on the SQL Server binaries that ... ADO.NET datasets is better than binding to joined tables for updates. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Opinions needed about the best "Middleware suite" kbmMW vs. RODA
    ... spend hours just first figuring out how does framework works, ... already using Chached Updates. ... I'm making heavy use of identity fields of sql server, ... What about master detail, where the primary field of the master record ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Problems with SQL MSDE after SBS SP1 upgrade!
    ... Thanks for updates. ... This newsgroup only focuses on SBS technical issues. ... | Subject: Re: Problems with SQL MSDE after SBS SP1 upgrade! ...
    (microsoft.public.windows.server.sbs)
  • Re: Opinions needed about the best "Middleware suite" kbmMW vs. RODA
    ... Those that answers this question best are "DA03 - Introduction to Schemas" ... > updates" like ado.net, and cascading delete, so if you delete a master ... > default sql, where the it autamaticly creates the sql (for ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Access vs SQL
    ... > to SQL. ... Are you using the database primarily as a storage place, ... If you have many updates then you need to constantly compact it. ... No additional cost to your clients. ...
    (microsoft.public.dotnet.languages.vb)