ork_with_Informix

7 Feb 2006 3:49 PM

Bea MarÃn

Hi all,

I have problems with CommandBuilder in NET Framework 2.0.

I am trying to update a table in Informix IDS 9.40 (client SDK 2.90 TC4, the
last one) using a dataadapter and a commandbuilder (vb.net). In NET Framework
1.1 my code works OK, but now I am migrating to Visual Studio 2005 and the
same code that worked before give me now this error: "Dynamic SQL generation
is not supported against a SelectCommand that does not return any base table
information.".

I read this error is produced when the table have not a key column, but my
table have one, so this is not the problem.

Any ideas? Maybe commandbuilder is different in NET 2.0?.

7 Feb 2006 6:03 PM

William (Bill) Vaughn

Yes, the CommandBuilder is different for 2.0 but the basic tenets are the
same. And yes, I expect that the CB is having trouble determining the
table's PK. That's how it generates the action commands.
That said, not many of us recommend use of the CB for serious production
applications. We quickly outgrow its limitations as our designs get more
sophisticated. I suggest that you simply hard-code the UpdateCommand and
other action queries.

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

Show quote

"Bea Marín" <Bea Ma***@discussions.microsoft.com> wrote in message
news:53635280-5A04-4822-9E2A-53BB0822577D@microsoft.com...
> Hi all,
>
> I have problems with CommandBuilder in NET Framework 2.0.
>
> I am trying to update a table in Informix IDS 9.40 (client SDK 2.90 TC4,
> the
> last one) using a dataadapter and a commandbuilder (vb.net). In NET
> Framework
> 1.1 my code works OK, but now I am migrating to Visual Studio 2005 and the
> same code that worked before give me now this error: "Dynamic SQL
> generation
> is not supported against a SelectCommand that does not return any base
> table
> information.".
>
> I read this error is produced when the table have not a key column, but my
> table have one, so this is not the problem.
>
> Any ideas? Maybe commandbuilder is different in NET 2.0?.
>