Thanks for you reply Sergey.

Ironically the EXE program that is causing the problem is part of my application launcher. Having it location on a network share was easier for my customer to support than having it installed on individual workstations. I have a generic installer for the FoxPro runtime files that I use for all my FoxPro projects. The only thing the customer needs to complete the application installation is a shared folder and then each workstation has a shortcut to the EXE file in that shared folder. The EXE does things like makes sure local copies of some files like the complied help CMH files are updated since there can be problems with those if they are run from a network drive also.

As a workaround I wrote a very short FoxPro EXE that can be run from their Windows 7 workstations and takes the path to the original shared folder (as a command line argument in a shortcut or from a configuration file). So I have a local EXE calling my original start program EXE on the network share and that is sufficient to make the SQL Server connection work again.