visual basic.net standard 2003 (ado.net)
From: ADO data adapter limit (limit_at_discussions.microsoft.com)
Date: 08/23/04
- Next message: Eric: "ADO connection state and object destruction Problem/Question"
- Previous message: Jim Cutler: "RE: Passing a binary(16) parameter to a stored procedure in C++"
- Next in thread: William \(Bill\) Vaughn: "Re: visual basic.net standard 2003 (ado.net)"
- Reply: William \(Bill\) Vaughn: "Re: visual basic.net standard 2003 (ado.net)"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 23 Aug 2004 13:09:06 -0700
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: Eric: "ADO connection state and object destruction Problem/Question"
- Previous message: Jim Cutler: "RE: Passing a binary(16) parameter to a stored procedure in C++"
- Next in thread: William \(Bill\) Vaughn: "Re: visual basic.net standard 2003 (ado.net)"
- Reply: William \(Bill\) Vaughn: "Re: visual basic.net standard 2003 (ado.net)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|