Thom,

>I think the core of the problem is that the class' textbook is using the Server Explorer wizard in VB.NET to create the SQL and associated parameter collections.<

I hate using wizards ... one of my main gripes with using them is that typically one never delves deeper into the resulting code to try and understand what's going on. That's the core problem. It's not that they generate bad code or anything, it's just that typically the code that is generated is not doing things the "right" way, just the "easy" way.

You've said that the course you were taking was an "advanced" course ... I would think they would show you how to do things without using wizards.

>>I'm a Fox programmer from way back, and I don't much care for what I'm seeing in .NET, or at least VB.NET.<

Well, I won't start any religious wars here <g>, but I prefer C#. I don't know what kinds of things are turning you off in .NET, but it's really not that bad. It may take some getting used to, that's all.

~~Bonnie




>Thanks for everyone's help.
>
>From what I can see, the problem is low-level in ADO.NET. I've traced into the dataAdaptor's Update() method and everything looks right. I've floated the code past a couple of "tutors" at school and everyone's eyes get real wide when they see what I've got... doesn't say much for the school does it?
>
>I think the core of the problem is that the class' textbook is using the Server Explorer wizard in VB.NET to create the SQL and associated parameter collections. It's easier to create than using SqlCommand and ExecuteNonQuery(), but when it breaks, you're screwed.
>
>I'm a Fox programmer from way back, and I don't much care for what I'm seeing in .NET, or at least VB.NET.
>
>>>"I love VB.NET"! It lets me do things that I should not and does not throw errors. Then after working for months it will blow up never to work again! So I like to use C# as it does not let me get away with "anything"! :)
>
>That's one of the things I see with VB.NET. As a professional developer, the instability of the language scares the hell out of me. I ran into a problem once where the syntax for control data binding had changed between ver 1.0 and ver 1.1. I could just see developing a major app, upgrading to the next version of VB and having the whole thing die because of a language compatiblity issue between the versions of VB. It could take months to track down all the problems.
>
>Again, thanks to all.
>
>Regards,
>Thom C.