Have alternative to CommandDataBuilder?

I realize that Microsoft not intend to fix problems of Commandbuilder:

+not deal with SQL calculated fields
+not deal with Identity field to retrieve it

and also cannot be inherit!

there someone wrote Alternative?

Cor
Sun Jan 21 03:37:52 CST 2007

Because you don't write something about it, use the DataAdapter wizard to
get your SQL code, it gives you endless possibilities.

In my opinion are you expecting to much from the Commandbuilder, it is just
an easy way of quick and dirty updating simple files. And in that if
fullfils its job very good in my opinion,

Cor

<mtczx232@yahoo.com> schreef in bericht
news:1169364657.605301.149630@s34g2000cwa.googlegroups.com...
>I realize that Microsoft not intend to fix problems of Commandbuilder:
>
> +not deal with SQL calculated fields
> +not deal with Identity field to retrieve it
>
> and also cannot be inherit!
>
> there someone wrote Alternative?
>

Cor
Sun Jan 21 05:08:30 CST 2007

Writing about the version that you are using

Miha
Sun Jan 21 07:41:44 CST 2007

Sure, use an ORM product that builds sql statements (and much more) for you
(I suggest LLBLGenPro) or use a template based code generator (such as
CodeSmith) to generate sql statements automatically from database metadata.
Or write sql by yourself.

--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

<mtczx232@yahoo.com> wrote in message
news:1169364657.605301.149630@s34g2000cwa.googlegroups.com...
>I realize that Microsoft not intend to fix problems of Commandbuilder:
>
> +not deal with SQL calculated fields
> +not deal with Identity field to retrieve it
>
> and also cannot be inherit!
>
> there someone wrote Alternative?
>

William
Sun Jan 21 13:45:06 CST 2007

Yes, as you've found, the CommandBuilder is pretty simple. It's designed for
very simple applications. You have found but two of the long list of issues
that it has. As a result, as developer's skills mature, they tend to outgrow
the CB. Some have written their own code generators. Some have simply used
the CB as a starting point and tuned the generated code to address their
specific issues. Consider that the entire TableAdapter/CB paradigm is built
around single table access. Many more serious relational databases don't
update a single table during an operation (a transaction) but have to update
several in series. This makes use of the simplistic CB approach unworkable.
To address this issue, developers migrate (eventually) to custom business
classes or to stored procedures that encapsulate the code and logic so that
the actual tables are never exposed.

This is all discussed in depth in my 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)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
-----------------------------------------------------------------------------------------------------------------------


Microsoft MVP, Author, Mentor
Microsoft MVP
<mtczx232@yahoo.com> wrote in message
news:1169364657.605301.149630@s34g2000cwa.googlegroups.com...
>I realize that Microsoft not intend to fix problems of Commandbuilder:
>
> +not deal with SQL calculated fields
> +not deal with Identity field to retrieve it
>
> and also cannot be inherit!
>
> there someone wrote Alternative?
>