Re: Maximum Fields in SELECT statement

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Brian Brown (BrianBrown_at_discussions.microsoft.com)
Date: 02/03/05 

Date: Thu, 3 Feb 2005 06:01:02 -0800

Hi Anatoly,

Sorry for the late reply but I decided to test this myself. I created a
table with all of the fields that you have below. Then I created a test
Windows Application and used the wizards to configure an oleDbConnection and
an oleDbDataAdapter. When I first pulled the table over to my form I
received the same error that you are getting. Then I expanded the
SelectCommand node and invoked the Query Designer on the CommandText
property. I unchecked the * and went down the list and checked every column.
Then I went in to the form_load and assigned hooked up the datagrid on the
form to the dataset filled by the dataadapter. It ran fine with no problems.
 At this point I went back to the database and added 4 more fields to it.
Then went back to the app and redid everything I have just written (being
sure to delete the old dataadapter and placing a new one on the form) and ran
it again with no problems.

Can you create a test form as I have descibed above and test it in the same
manner? If you still get an error please reply to this post describing
exactly what the error is and the exact steps that you have taken, so I can
repeat it.

I hope this helps.

Relevant Pages

  • Re: Error in code?
    ... Take a look at the constructor for your DataAdapter. ... What IS the CommandText? ... The code works fine for a datareader but the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: using dataadapter.update changes the insertcommand.commandtext
    ... changing the commandtext and from the code here, ... >I have a dataadapter where i have changed the insertcommand.commandtext to ... the dataset's identity column is not updated with ... > is in the database, and when I inspect the insertcommand.commandtext right ...
    (microsoft.public.dotnet.framework.adonet)