Hi,
The ODBC error that you describe is definitely unusual, I've never heard of that issue.
One test that comes to mind is to try and connect to the GP SQL server without using an ODBC DSN. If you see the correct database list, then that would seem to indicate an issue with ODBC. If you still see the incorrect list, then that would seem to indicate a DNS issue or a SQL Server configuration issue.
If you have Excel 2007, you can create a data connection to SQL Server. In a new Excel workbook, create a connection to the GP SQL instance. If you know the sa password, you can use that, or if you are a domain / local admin on the server, then you can use Windows authentication.
Depending on the results of that test, one setting to check on both of the SQL Servers is the server name. If either of the servers were cloned or were ever renamed, that may be causing some confusion with the SQL Browser service.
Log in to each SQL Server and for each SQL *instance* on each machine, run the following two queries:
select @@servername
sp_helpserver
Check the results to see if they match the instance name that you expect.
Also verify that the SQL Browser Service is running on both SQL Servers.
Let me know if these tests turn up any additional info and we'll proceed from there.
As for the second "BCP" error when launching GP on Windows 7, I believe that this is an unrelated issue. Try right mouse clicking on the GP Utilities icon and selecting Run As Administrator. You can also try completely disabling User Account Control on the Win 7 machine. Let me know if that resolves the error and gets Utilities to launch.
Thanks,
Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified Professional