>Bill,
>
>>>I am not using the CommandBuilder! Should I be?
>
>Well, the error message:
>
>Exception Details: System.InvalidOperationException: Dynamic SQL generation for the UpdateCommand is not supported against a SelectCommand that does not return any key column information.
>
>indicates that you're using the UpdateCommand and that it hasn't been properly generated, which means that the CommandBuilder is being used, because the CommandBuilder automatically generates an UpdateCommand for you. Part of my problem with answering this question is that you're using MM which throws in an additional layer of complexity which I know nothing about.
>
>So, Kevin, or someone who uses MM, would be a better choice for answering this question, but since you directed it at me, I thought I should at least give you a reply.
>
>Does MM possibly uses CommandBuilder behind the scenes? I don't know.
>Is it optional to use so that you can roll your own UpdateCommand? I don't know.
>Is it set up so that you don't even have to use the UpdateCommand but can totally roll your own Data Updates (which is what I do, BTW)? I don't know.
>These are the kinds of answers you need.
>
>~~Bonnie

Thanks, Bonnie!