>Yes, there should be some type of event or place where you can add code to set the app role each time a connection is made.

Wouldn't it be kind of slow to make 2 ODBC calls each time I need to access the database? 1 for the SetAppRole and 1 for the actual work.



>Not sure how pooling comes into play on a single user app like winforms. I think Mike Levy told me once that the connection retains the app role with pooling even after the app closes the connection. If this is the case, on making the connection you can check to see who the user is. I am pretty sure one of the function returned the app role name.

Again, making multiple ODBC calls each time a user click on the nav buttons seems to be inefficient. In fact, I can't even make a SELECT user_name() call to SQL after the SetAppRole call, EVERYTHING error out with "General Connection Failue".