|
Re: SqlCommandBuilder: msg#00341windows.devel.dotnet.winforms
Have a look at SQL profiler and see what its doing. It's listed in my book and, IIRC offhand its: SET FMTONLY ON -- do not return results, only metadata SET NOBROWSETABLE ON -- use "browsetable" format to return additional -- metadata, but don't use a physical browse table SELECT.... -- execute query SqlCommandBuilder is public, but sealed/NotInheritable Cheers, Bob Beauchemin http://staff.develop.com/bobb -----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 7:37 AM To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx Subject: Re: [DOTNET-WINFORMS] SqlCommandBuilder Unless you're telling me to go to the connection to get the error information :) ___________ 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 -----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, 25 February, 2004 09:32 To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx Subject: Re: [DOTNET-WINFORMS] SqlCommandBuilder I know what my connection string is.. I'm using Integrated Security. I didn't' anticipate/(think through) that it (is probably) going directly to the tables to get parameter information on a SP... It must be going to a system table or my user tables... All of which the general users have no access to. ___________ 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 -----Original Message----- From: Discussion forum for developers using Windows Forms to build apps and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx] On Behalf Of Adam Straughan Sent: Wednesday, 25 February, 2004 09:04 To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx Subject: Re: [DOTNET-WINFORMS] SqlCommandBuilder You need to look at the SqlConnection object, which is where the users connection security is setup via the connection string. adam > -----Original Message----- > From: Vince P [mailto:pacelvi@xxxxxxxxxxxxx] > Sent: 25 February 2004 15:15 > 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 > |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: SqlCommandBuilder: 00341, Vince P |
|---|---|
| Next by Date: | User v Custom Controls: 00341, Richard Heintze |
| Previous by Thread: | Re: SqlCommandBuilderi: 00341, Vince P |
| Next by Thread: | Web Service accessing SqlServer WAS: SqlCommandBuilder: 00341, Greg Robinson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |