>>>
>>>(Weird) UPDATE: On a network share I am able to run the EXE when there is NO config.fpw. As soon as I include a config.fpw the exe cannot connect to the backend SQL Server database.
>>>I have spent the morning trying to find different system variables, SETs but haven't pinpointed it yet.
>>>BTW, I do not have a config.fpw in my VFP home directory. If one does not exist, is there an internal one that VFP uses?
>>>Thanks Al for pointing me to the config.fpw!
>>>Ed
>>
>>This article will answer most of your questions. http://rickschummer.com/blog/2008/06/vfp-include-configfpw-in-exe.html
>
> LOL, that's the article that got me into trouble in the first place! I used Rick's stripped down version of the config.fpw and finally figured out it is the config.fpw itself that is causing issues (even a stripped down one). There must be something VFP IDE loads (or perhaps the VFP.EXE has certain permissions on my company network) that is different than my compiled exe.

Actually your last point is a good one. If your network is fairly tightly locked down you may have firewall rules blocking SQL Server traffic; its communication requirements are at http://support.microsoft.com/kb/287932 .

A firewall on your machine with outgoing rules may allow VFP9.EXE but not allow your compiled EXE.

It's less likely a firewall rule on the machine hosting SQL Server is causing the problem but if it's granular to the point of controlling access by program by computer, then it could be worth looking at.