>I am wondering if anyone has any suggestions...
>
>We have a Visual Foxpro 9 Client / Server application that is run on a thousand desktops that connects to a SQL 2005 server.
>We also have C#.Net Apps too that this scenarion falls under as well...
>
>We embed the SQL Server, Database Name, User ID and Password into the application so that the user that runs the application can access the SQL Server database.
>
>The LAN ID from the Windows workstation is used to query a table in the applicationj to see if the user has access to the application, if that LAN ID does not exist in the table it does not allow the application to run.
>
>We are being told now that I cannot know the User ID and Password and can no longer embed it into the compiled EXE file.
>Only 2 people know the SQL Server ID and Password we are using. This now has to be 1 person, the DBA.
>
>Any suggestions on how I might go about doing this?
>
>I do not think we can go with Windows authentication because that would allow people using Word, Excel, Access authentication to the database via Windows authentication and change the data outside of our application. Plus windows authentication would be a administrative nightmare with adding people and people leaving the group etc...
>
>Outside of me giving the DBA my source code, showing him where to change the SQL Server user ID and password and having him compile it himself... Does anyone have any ideas??
>
>Thanks!
>Bob


I am not a SQL server expert but isn't that like saying I expect you to login to something but you are not allowed to have a userid and password? What do they expect you to do with that?

Is the data access being done all through stored procedures? If so would they let you have a userid and password that only has access to the stored procedure execution needed for the application?
Tim