Re: SqlCommandBuilder

Note to Vince, do not use the CommandBuilder in production.

This is a Private class and the implementation can change for one. Your
table must contain a PrimaryKey for two. You incur a performance penalty for
the roundtrip when using DeriveParameters.

There are more but I will stop there.



-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx]On Behalf Of
Vince P
Sent: Wednesday, February 25, 2004 10:15 AM
To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx
Subject: [DOTNET-WINFORMS] SqlCommandBuilder


One of my WinForms is throw up errors about Dynamic SQL not being authorized
on users who aren't DB Admins.

This particular WinForm uses a class in my data tier that uses a
SqlCommandBuilder to retreive SqlParameters of a SqlDataAdapter (of a Stored
Procedure)  (note: the form and data tier are running user's box, the DB
itself is remote)

I'm going to work under the assumption the SqlCommandBuilder is using the
User's Windows identity to run some Sql against the DB tables, and since
those users don?t have table access, the error is being thrown.



___________
Vince P  http://66.93.114.145/vince/

MSN Messenger: this address
AIM: pacelvi

"Nobody said it'd be easy. Nobody said that it would be this hard." -
Coldplay