Re: MsAccess to SqlServer: sp_setapprole problem

On 27 jun, 19:13, Rich P <rpng...@[EMAIL PROTECTED]
> wrote:
> The issue you are experiencing is caused by the limited capabilities of
> ODBC. =A0For basic operations ODBC is an easy way to connect an Access
md=
b
> to a sql server backend. =A0But once the operations get a little more
> sophisticated - as in your case - the limitations of ODBC become
> apparent. =A0The workaround is to switch to ADO - this is why ADO was
> developed - =A0to overcome the limitations of ODBC.
>
> you can execute sp_setapprole through an ADODB.Command object very
> easily (just make a reference in Tools/References to Microsoft ActiveX
> DataObjects Library 2.5 or higher)
>
> Sub xyz()
>
> Dim cmd As New ADODB.Command
> cmd.ActiveConnection =3D "Provider=3DSQLOLEDB; Data
> Source=3DyourSrvr;Database=3DyourSvrDB;Trusted_Connection=3DYes
> cmd.ActiveConnection.CursorLocation =3D adUseClient
> cmd.CommandType =3D adCmdStoredProc
> cmd.CommandText =3D "sp_setapprole"
> cmd.Execute
> cmd.ActiveConnection.Close
>
> End Sub
> Rich
>
> *** Sent via Developersdexhttp://www.developersdex.com***

Thx. But I would realy like to stick to DAO for the application
itsself. I know DAO isn't the nr 1 technology any more, but I know DAO
well and don't do that much programming work as I used to do in the
past. For new stuff I concentrate on the Dotnet framework with it's
Ado.Net.
What would be nice is if the ADO code you send would have its effect
on the connection DAO/ODBC uses. That would be perfect, but as most
things in life 'perfect' isn't often the case. I'll test it anyway....