The easiest is to make objects that use Enterprise Services and place the
compiled assembly in Component Services (COM+). Here you can declaratively
assign a user for the component to run under. One caveat. If the assembly
calls other .NET assemblies, you will likely be sticking them in the GAC.
With threads, you have the ability to spawn a thread with proper
permissions. You will have to set up a WindowsIdentity object, assign it to
the property of the WindowsPrincipa l object, which is assigned to the
CurrentPrincipa l property of the thread you are running data access under.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** *************** *************** ***
Think Outside the Box!
*************** *************** *************** ***
"Flavio" <an*******@disc ussions.microso ft.com> wrote in message
news:E5******** *************** ***********@mic rosoft.com...
I can't use ASPNET user, is there any way to maipulate the system to
connect with a different user on a trusted connection?
Falvio