On Sat, Nov 29, 2008 at 2:45 PM, Scott King <[EMAIL PROTECTED]> wrote: > I'm developing a client/server application in VFP9SP2 with a SQL Server 2005 > database backend using ODBC. The User Interface, business, and data access > layers are logically separated but physically all currently reside in a > single EXE. > > The customer requires windows authentication and wants to use a service > account for database access in SQL Server. > > I am currently storing encrypted copies of the User ID/Password for the > service account and using api calls to LogonUser(), > ImpersonateLoggedOnUser(), and RevertToSelf() wrapped around the call to > SQLStringConnect(). > > What other options do I have for making the connection using the service > account's credentials? > > Also, are there any negative side effects/consequences of the method I am > currently employing? ------------------------------------
This seems normal and from your functions listed you are on target. In a .NET world all of these requests would be in the web or app . config file. Their request and your solution seem right in line. -- Stephen Russell Sr. Production Systems Programmer Mimeo.com Memphis TN 901.246-0159 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
