Re: visual basic.net standard 2003 (ado.net)
From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 08/24/04
- Next message: William \(Bill\) Vaughn: "Re: ADO - Copy Data from one data source to another via VB6"
- Previous message: Wayne Froese: "RE: DBF file - Concurrency violation"
- In reply to: ado.net: "Re: visual basic.net standard 2003 (ado.net)"
- Next in thread: John Doe: "Re: visual basic.net standard 2003 (ado.net)"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 24 Aug 2004 08:14:20 -0700
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. __________________________________ "ado.net" <ado.net@discussions.microsoft.com> wrote in message news:C99B0424-4AD1-463A-989F-A797E1AE6AAE@microsoft.com... > 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. > > "William (Bill) Vaughn" wrote: > >> 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 >> limit@discussions.microsoft.com> >> wrote in message >> news:D486C190-4B8C-4CA1-AFFB-B86D1B424BF2@microsoft.com... >> > Why is there a 100 field limit when using the adapter wizard to >> > configure >> > a >> > data adapter. I have a database that has over 200 fields and need the >> > ability >> > to add, update and delete. The wizard fails with an error message >> > "There >> > were >> > errors configuring the data adapter". I do not understand how Microsoft >> > can >> > provide the ability to have 200+ fields in Access or SQL and not >> > support >> > them >> > with ADO that they have been highly promoting. I never had a problem >> > with >> > DAO >> > using VB6. What's up! frustrated with .net >> >> >>
- Next message: William \(Bill\) Vaughn: "Re: ADO - Copy Data from one data source to another via VB6"
- Previous message: Wayne Froese: "RE: DBF file - Concurrency violation"
- In reply to: ado.net: "Re: visual basic.net standard 2003 (ado.net)"
- Next in thread: John Doe: "Re: visual basic.net standard 2003 (ado.net)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|