>>Hi,
>>
>>I would like to understand better how VFP 9 application connects to SQL Server. Here is the situation:
>>
>>The application resides on the customer server (VM) (in folder c:\applfolder). SQL Server is in the same box (same VM).
>>The application is set to connect to SQL Server using SQL Server authentication. The application has a configuration file where the User ID and Password for the SQL Server are set. So that application is using these credentials to connect to SQL Server.
>>
>>When I RDP to the server I can start the application and it connects to the SQL Server, no problem.
>>
>>When any user (who is on the LAN) starts application (by loading the application .EXE from the Shared folder, applfolder) they get error that they cannot connect to the SQL Server.
>>
>>What permissions should the desktop users have to the SQL Server in order to connect? Or is there another explanation of this problem?
>>
>>TIA.
>
>
>The current VM has probably a NAT network - which means that that VM is visible to the host and other VMs running in the host
>
>If you set the network to Bridged - all the computers on the network will be able to 'see' that VM

First, thank you. The network terminology you use (NAT, Bridged) goes over my head. But all desktops can "see" the VM because they can use the application when the application is not attempting to connect to SQL Server. The problem happens when I change the application to connect to SQL Server (instead of using VFP data). I am thinking that perhaps (and I don't know for sure) that the dekstop user IDs have to be in the SQL Server Logins. Does it make sense?