Of course I don't fully understand the project context, but I don't see
a need to do it that way anyway. The command object is more useful for
SQL Passthrough and stored procedures, but I never use it to create recordsets
anyway. As with many things with ADO, you always have to work around the 'gotchas'; at least there are so many ways to 'skin the cat' that it isn't a problem.

Ed

>>I had ran into a similar problem. See MS KB Article Q188857; hopefully
>>that will help. The problem still exists in ADO as far as I know.
>
>I find it strange that commands created by the designer allow updates!!!