>>>Thank you for your message.
>>>Now - just this morning (since the customer is in Europe) - I received a new requirement. Now the customer wants a user to enter both the AD username and AD password into my VFP application. And my VFP application to check if this is a valid user. Initially I thought that they would not want a user to enter his/her password into the VFP application.
>>>So, I am back to Tamar's link where the VFP application should create a query to the AD and validate a user.
>>>I will need to find the name of the AD/SQL Server DB to do that.
>>
>>I question the need for this. If the user has already signed in to a domain-joined computer. their session is already authenticated. Why should they need to authenticate again from within your app, with the same credentials?
>>
>>If access privileges within your app depend on the AD username, you already have that, and you know they've already successfully authenticated against AD using that username.
>
>They have what they call "shared PCs". So, they would like various users to log into my application with the same username and password they use for their AD log in. So that each user will only have to remember one username and one password.
>So, I will have to build a feature where the application will validate if this or that user is already in the AD.

Multiple users can sign in (one at a time) on a "shared" computer - one signs out, another signs in.