>>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?
>
>Are you sure that connection string is exactly the same in both cases?

Yes - I've verified that the connection string is both the same and correct.

I ran the application .exe inside VFP and it works correctly.The most recent time I ran the .exe independently, I used ODBC tracing, and got a SQL.LOG file that included the following:

2108            1654-b20	ENTER SQLDriverConnectW 
		HDBC                0098BD68
		HWND                00000000
		WCHAR *             0x6FD6B1C0 [      -3] <Invalid string length!>
		SWORD                       -3 
		WCHAR *             0x6FD6B1C0 
		SWORD                       -3 
		SWORD *             0x00000000
		UWORD                        0 <SQL_DRIVER_NOPROMPT>

2108            1654-b20	EXIT  SQLDriverConnectW  with return code -1 (SQL_ERROR)
		HDBC                0098BD68
		HWND                00000000
		WCHAR *             0x6FD6B1C0 [      -3] <Invalid string length!>
		SWORD                       -3 
		WCHAR *             0x6FD6B1C0 
		SWORD                       -3 
		SWORD *             0x00000000
		UWORD                        0 <SQL_DRIVER_NOPROMPT>

(2108.exe is the name of the application.)

Anyone know how to read this, and if so, what does it mean?