BIG BUG in SqlCommandBuilder.DeriveParameters

  • Thread starter Thread starter Marc Scheuner [MVP ADSI]
  • Start date Start date
M

Marc Scheuner [MVP ADSI]

Folks,

Try this: if you have a stored proc on your SQL Server 2000 with a
parameter of type TEXT, and if you then use a
SqlCommandBuilder.DeriveParameters call to determine the stored proc's
parameters, you'll end up getting an entry for that parameter in
question of type "VARCHAR", with a size of 2 billion (2 GByte of
chars).

Needless to say, this doesn't work - any idea why SqlCommandBuilder
doesn't recognize TEXT parameters, and properly convert them to
parameters with a SqlDbType of "Text" ??

Anyone else seen this? We're using VS.NET 2002, with the 1.0 .NET
Framework. Hsa this been fixed in the 1.1 .NET framework maybe??

Thanks!
Marc

================================================================
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)inova.ch
 
Take a look at my article on the CommandBuilder. You're really better off
rolling the Command Parameters collection yourself.
http://www.betav.com/msdn_magazine.htm


--
____________________________________
Bill Vaughn
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.
__________________________________
 
Take a look at my article on the CommandBuilder. You're really better off
rolling the Command Parameters collection yourself.
Click to expand...

Geez.... any hope that .NET 2.0 will fix these shortcomings??

Marc

================================================================
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)inova.ch
 
Back
Top