>The SQL Server is on my PC. So I suppose this IP indicates IP of my PC. So my question is, would the customer fire wall check for this? Or because their PC where SQL Server resides is on their network it won't be a problem?
>

Generally firewalls do not check for activity that only acts on your localhost address. YMMV on that.

If machines other than the SQL Server machine need to access the SQL Server data, then you need to allow through TCP port 1433 on the firewall on the SQL Server machine (if there is one). SQL Server needs to be configured to enable TCP protocol.

>
>>Isn't it IP address of PC with SQL Server you're connecting to?
>>
>>>
>>>I am testing my VFP 9 application that uses SQL Server database. Whenever I start the application executable Comodo (personal fire wall) shows the message that MyApp.exe is trying to connect to Internet ( 10.1.10.28 Port: ms-sql -TCP) ) Parent: cmd.exe. I am concerned that this will happen on the customer computer/network and their fire wall may not allow the connection. How do you suggest to deal with it?
>>>
>>>TIA.
>>>
>>>PS And also curious why is the parent CMD.EXE? Is it because I start the application form the command prompt?