>>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.

Any thoughts?