I am using the FoxPro OleDB driver through ADO.NET and getting a "SQL
Statement too long" error.
If I Update one column, The Command Builder builds a SQL statement with all
the columns which I presume is too long for the driver to handle given the
error. Is their a way to either expand the SQL Buffer beyond the 2048
default, or have command Builder only include the columns necessary for the
update? I presume if a Insert a record I will also hit this limitation, Is
their a way to break up the command or some other means of updating the
tables.
Thanks in Advance,
Mike Pisano
--Bob
"Mike Pisano" <Mpi...@ConcordiaFreight.com> wrote in message
news:e1sEqzquCHA.456@TK2MSFTNGP09...
As an alternative, you can create your own UpdateCommand, insetad of using
the CommandBuilder to generate an UpdateCommand automatically.
For more information and sample code, please refer to the documentation at
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconupdatingdatabasewi
thdataadapterdataset.asp?frame=true
Gary
This posting is provided "AS IS", with no warranties, and confers no
rights. Enjoyed ASP.NET? http://www.asp.net
I was afraid of that, What a Dumb limitation.
What happens when you need to update a field that is larger then 2k as in a
Memo field?
Thanks Again,
Mike
It seems to a limitation of the FoxPro OLEDB provider. I am doing some
further research on it and will post back later.
I appreciate for your great patience.
Best Regards,
I am working with the appropriate team on this case. I will post here back
if there is any update.
Thanks for your great patience.