application role or at least connection properties

[wlrthjoilihjw]

hi,

I'm using RDC (CR9) in my VB6 applications to run reports against SQL Server 2000 database. Now I have to adapt all apps to run under sql server application role.

Question #1: is there any way to activate an application role for the database connection used by RDC? My database users have no permissions on tables, views, stored procs etc, only the application role does. How can I make it work with the application role? I've search the web, but it seems to be no solution for that

Question #2: my application role problem could be solved by using a generic database user in report connections, with all necessary permissions and a password hard coded in my application. But my views and stored procedures do need to know the real user id of the person working with the application. I can't pass this id as a report parameter for some reasons. I would like to specify this id in the connection string used by RDC, e.g. as the value of the Application Name connection property. But it doesn't work - in the sysprocesses table I still see my application name instead of my value. Is there any way to make RDC "understand" my efforts? Any help would be greatly appreciated...

TIA

 

[vidru]

There's a whitepaper on the inability to use an application role as the login using the RDC here:

http://support.businessobjects.com/library/kbase/articles/c2010048.asp

Crystal is going to need the userid/password as either a valid SQL Server login, or if you're using Windows Authentication, a valid Windows login.

-dave