DataAdapter Select Statement

To all

I'm VS2003, when I try and create a dataadapter with more than 100 fields (either through drag-n-drop or manually) I received "There were errors configuring the dataadapter".

Since the table is in SQL 2000, I tried using: "Select * From inmast" which returns 143 columns and all rows from the table

I even tried importing the table in MS Access 2003 with the same results.

If I reduce the # of fields to 100 or below the dataadapter will work as normal

Help

David Davis

[489 byte] By [DavidDavis] at [2008-2-14]
# 1
Hi,
Could you provide steps to reproduce it? Pls report it as a bug in Product Feedback Center...

PS. Keep us posted...

cheers,
Paul June A. Domag

PaulDomag at 2007-9-8 > top of Msdn Tech,Visual Basic,Visual Basic Language...
# 2

Paul June A. Domag

I have posted the full description (prior post) and the steps to reproduce in the Product Feedback Center also.

The steps to reproduce are:

1. Find a table with more than 100 fields
2. Drag and Drop a table from "Server Explorer" (Can be Access or SQL)
3. Manually configure (via wizard) a dataadaptor (Can be Access or SQL)

either will produce the error "There were errors configuring the dataadapter".

The select statement looks like it is configured correctly but the update, insert and delete aren't configured at all.

Thanks

David Davis

DavidDavis at 2007-9-8 > top of Msdn Tech,Visual Basic,Visual Basic Language...
# 3
Hi,
Hmmm... Puzzled...
Tried it and it happens...
I'll try to look-up on it. I'll just keep you posted if I could come up with some solution on this...
cheers,
Paul June A. Domag
PaulDomag at 2007-9-8 > top of Msdn Tech,Visual Basic,Visual Basic Language...
# 4
Paul

Here is what I got back from the people at Product Feedback Center.

Dear David,

the error you are seeing is a limitation of the data adapter configuration wizard in Visual Studio 2003. In your application if you really need to consume all 100+ columns from your table, then you have to configure the data adapter manually (by setting its properties via property grid). In most cases I have seen the programmer could get away with fetching data from a subset of table columns (the subset will vary depending on the data needed by various parts of your application). This has a nice side effect of improving application performance too (because less data is pushed through the network). We have no plans to change this limitation in upcoming service releases for VS 2003.

In VS 2005 we no longer have this limitation. Still, we recommend to limit the data fetched by the application as much as possible.

Hope that helps,
Karol Zadora, Visual Studio Development Team

--

Dave

DavidDavis at 2007-9-8 > top of Msdn Tech,Visual Basic,Visual Basic Language...
# 5
Hi,
Thanks for keeping us posted. So that's a limitation. Haven't even seen it in the documentation... Well, I guess you'll be forced to use the VS2005 after all... Big Smile
cheers,
Paul June A. Domag
PaulDomag at 2007-9-8 > top of Msdn Tech,Visual Basic,Visual Basic Language...