FWIW, I connect several applications I have to multiple SQL Servers without problems using SQL Passthrough, so this definitely works.

You might want to check your drivers used, especially if you use a DSN to connect. Make sure you're using the drivers that are compatible with the latest version you're using (ie. SQL 2008).

I suspect too, if there is some sort of driver problem that if you connect to SQL 2008 first it will use the latest drivers that should also work with SQL 2005.

I've never seen this issue personally and I've done quite a bit of cross server application code, so this might be something isolated to your config.

+++ Rick ---

>To all who might know what is needed in this case -
>If I connect to SQL Server 2005 in the manner described below, all works a-okay.
>But when connect the same program to SQL Server 2008 on a Wni Server 2008 platform problems occur for which I have no idea where to turn for solutions.
>
>My VFP Program accesses SQL Server via ODBC 32 bit version in both the SQL 2005 and 2008 cases.
>When I connect to the main database, all works okay no matter whether is is running under SQL 2005 or SQL 2008.
>
>But when access a 2nd database (the archived history database) get the following error messages -
>"Specified DSN contains an architecture mismatch between the Driver and the Application" or
>"Source Name Not found and no Default driver specified" or
>The server Pricipal "User-1" is not able to access the database "Archived Data" under the current security context.
>
>These errors occur whether I access the archive by calling SQLCONNECT or if I simply ID the archive database as part of the table's name in the SELECT statement.
>
>Maybe I need to do something different in ODBC or is there a parameter or driver needed for the VFP engine?
>
>I sincerely thank all those who might have a suggestion or idea where I have gone astray.
>
>Rich Balluff
>RLB Associates
>(916) 663-6285 office
>(408) 396-0035 cell
>email rlb35@sbcglobal.net