Hi;

I am coming from an Access environment where 
the connection to the database stays open and
once a user has logged in to an application role 
the user has the permissions of that role for
subsequent operations. I have been trying to
figure out how to arrange for use of application
roles in the ASP.NET environment where each 
operation seems to need to grab and initialize
a new connection to SQL Server. I though I had
it figured out as a matter of opening a connection,
executing a command to run the stored procedure
that logs in to the role, leave the connection
open, and then do the SQL operation that actually
needs to be done. However, while that approach
seems to work when I am running the debugger, it
fails with general network errors when I try to
run normally. I have a feeling that I am missing
out on something. Suggestions? Thanks.

Lou