Update to Bill Vaughn's DACW article

[Earl]

For Bill or anyone else reading, what would be the equivalent steps shown in
his article
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnadonet/html/commandbuilder.asp)
to creating the DACW in VS2005 -- particularly if you are not using the
datagrid or even if you did not want a typed dataset?

 

[William \(Bill\) Vaughn]

The DACW is still there... it's just hidden. It can be added back to the
toolbox (Add Items) and run as it was in 2003.

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

 

[Earl]

Thanks Bill. Does the fact that it is hidden mean there is a better way of
creating the Insert/Update code than the DACW?

 

[William \(Bill\) Vaughn]

The DACW is hidden because MS thinks that the TableAdapter configuration
wizard is a better choice. Frankly, I don't agree. There are still
situations where the DACW is a better choice. I just finished a chapter on
this for my new book which should be on the streets in late summer. If you
remember the article, you'll know that I don't like the way that the
CommandBuilder generates update logic. I muchly prefer to use my own SPs to
execute these commands.

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

 

[Earl]

Thanks Bill, that answered my question precisely. CommandBuilder has always
sucked and if the TableAdapter is an evolution of that path, then I'll stick
with the DACW.

 

[William \(Bill\) Vaughn]

The CB has been improved and it does (now) recognize some simple TimeStamp
scenarios. However, it quickly breaks down when the query gets complex or
you evolve to stored procedures.

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

 

[Earl]

95% are stored procedures, and the DACW is working well now in VS2005, so
I'll stick with what works.

 

[Cor Ligthert [MVP]]

Bill,

I am not be so negative about the dataadapter as you seems to be in this
message, that it is created as a seperated completer class is at least one
advantage that is not in version 1.x. (I am talking about winform 2.0,
ASPNet makes a complete closed book).

That there is still a lot to do in that area is in my idea obvious (By
instance I can not find a way others than in a second step to create a
selective Select)

Cor

 

[William \(Bill\) Vaughn]

Ah, perhaps you should re-read the response. I think the DataAdapter is fine
for many situations. It's the reliance on the CommandBuilder that I
discourage.

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

 

[Cor Ligthert [MVP]]

Bill,

Maybe I did read this before your reply in another way.

The DACW is hidden because MS thinks that the TableAdapter configuration
wizard is a better choice. Frankly, I don't agree. There are still
situations where the DACW is a better choice.

Rereading the last sentence and make it more significant I can now agree
with that text.

Cor