visual basic.net standard 2003 (ado.net)

visual basic.net standard 2003 (ado.net)

Post by Bil » Wed, 25 Aug 2004 07:50:24


I suggest that you look more closely at your database design. I virtually
all cases when we've seen designs with this many columns it's because the
database is not normalized. Since an average (albeit wide) normalized
relational table might have 20 or 30 columns, 100 is excessive.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________

"ADO data adapter limit" <ADO data adapter XXXX@XXXXX.COM >
 
 
 

visual basic.net standard 2003 (ado.net)

Post by YWRvLm5ld » Wed, 25 Aug 2004 22:17:03

Normalizing my database did not answer my question. As to why did Microsoft
limit to 100 fields on the data adapter wizard, but give the ability for more
than 100 fields in a single database table. It would take massive coding
changes to restructure my database. It was working fine in VB6 with DAO. I
still do not understand this limit. Are there any plans by Microsoft to
increase the limit. Or is this a bug? Could you clarify further. Thanks.

 
 
 

visual basic.net standard 2003 (ado.net)

Post by Bil » Thu, 26 Aug 2004 00:14:20

I can't speak for Microsoft. Several of their folks lurk here so perhaps
they can answer you.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________