>>>I've been testing an application that involves connectivity to SQL Server. When the application is compiled as an .app file and run inside VFP, connections initiated by SQLStringConnect() work just fine. However, when the application is compiled as an .exe file and run independently, after stalling for a long time, the attempt to connect fails.
>>>
>>>I'm stymied...
>>
>>I agree with Cetin's comment. FWIW, you can use AError() to determine error numbers/messages when any Vfp SQL*() function fails, it's useful for unsuccessful SqlExec() lines as well as failing SQLStringConnect() etc.
>
>According to AError(), the connection attempt is timing out, which I suspected intuitively. The connection string looks correct, and when I switch back to compiling the application as an .app, it continues to work correctly. Most of the research I've done indicates that there's something going on at the server end, but that doesn't make sense in the context.
Are you running the .EXE and the .APP from the same computer, under the same user account? If not, maybe it's a permissions or firewall issue.
Also, some antivirus products real-time scan .EXEs, but probably don't do .APPs. You could try disabling real-time scanning to see if that makes a difference.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up