SqlException

  • Thread starter Thread starter Brian Toothill
  • Start date Start date
Tons of things. A bad connection string, unable to open the database,
connection timeout, bad format of the commandtext etc.

I'd check my connection and check the update logic that you have in place.
If you are using a command builder, you need a PK for it to generate update
logic as well.
 
I would profile the operation and see what SQL Server's being asked to do.
What about the other properties of the SqlExecption? What are you trying to
do? How are you trying to do it? This isn't much to go on. It's like calling
the vet and telling him that your cat died and you want to know why--but you
failed to tell him it was hit by a beer truck. ;)

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