From: matthew.wells@firstbyte.net   
      
   I didn't mean to sound unappreciative.  I'm very grateful for suggestions   
   whether they work or not.  I'm just glad you're not one of those people that   
   reply with "Have you looked at the help?".   
      
   --   
   Matthew Wells   
   matthew.wells@firstbyte.net   
      
   "Erland Sommarskog"  wrote in message   
   news:Xns9D395C0EB9F62Yazorman@127.0.0.1...   
   > Matthew Wells (matthew.wells@firstbyte.net) writes:   
   >> I appreciate the response, but I don't think this helps.  A regular user   
   >> is definitely logged in so a service user is out.  I did a trick a few   
   >> years back where I added "WSID= " + CurrentUser to the connection string   
   >> and then used @@Host_ID to get the user.  Seems really lame.  I was   
   >> really hoping there was a more logical way.   
   >   
   > I'm sorry if my response was not helpful enough, but since I only get a   
   > glimpse of your environment, it's difficult to say which ideas that would   
   > be workable. The one thing I can say with certainty is that if you are   
   > logged into Windows as user X, you cannot log into SQL Server with   
   > Windows authentication as user Y. This is a fundamental thing. Windows   
   > authentication works from the principle that Windows have already   
   > authenticated you, and that's why SQL Server lets you in.   
   >   
   > --   
   > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
   >   
   > Books Online for SQL Server 2005 at   
   > http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx   
   > Books Online for SQL Server 2000 at   
   > http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)