I tried that to one of our servers (filling in our server UNC paths as appropriate) and it worked fine. I tried with a free table, and one in a DBC and it worked.

[1, 2] = Connectivity error: [Microsoft][ODBC Visual FoxPro Driver]File 'temp.dbf' does not exist.
[1, 3] = [Microsoft][ODBC Visual FoxPro Driver]File 'van.dbf' does not exist.

That confuses me, because you don't have "van" in your SQLCONNECT statement. Or do you?
I know, you don't want to share your actual addresses. But I can't see where that van comes from.
I deliberately got the path wrong in the SQLCONNECT and the table name was the same in both error array elements.

Do you have any references to that other table in index expressions?
Or any rules/triggers in the database?

That's all I can think of, something that expects the other table to be open while eveluating the SQL.