Patrick,

I'm one of those who, as a rule, don't like wizards and stuff that's generated for me (with the exception of Typed DataSets), so the whole CommandBuilder thing turns me off. I like better control of it. The end result of me doing it myself is a heckuva lot faster anyway ... the CommandBuilder requires an extra trip to the backend to get metadata to figure out how to construct your insert/delete/update commands.

~~Bonnie


>You did provide some links earlier that I think had some sample of "roll your own" updates. This is mostly a throw away project so I not sure if I will take that route. I recently created a simple little project in VFP and I was going to try to recreate in .NET for fun/learning.
>
>Most of the examples I worked with have been using static data is MSSQL or Jet/Access and I am disappointed .NET is not more flexibale with the built-in classes to adapt from that norm without having to dump them and roll your own.
>
>Thanks for your help on this,
>
>Patrick
>
>
>
>>Ah, now we hear the rest of the story. <g> If I recall correctly (and this old brain is starting to forget things, so forgive me if I've got the particulars mixed-up), this is one of the reasons that using the CommandBuilder with VFP is problematic.
>>
>>If you don't have any PK's then you can't use the CommandBuilder and you'll have to roll your own, as I've suggested in a few of my other posts lately. I don't have time at the moment to look for links to those posts (I'm late for an appointment), but I'll post some links when I return, if you haven't found them yourself.
>>
>>~~Bonnie
>>