[AccessD] Linked ODBC, Moving App Between Computers

Yes.  When you link a table via ODBC, Access hard codes the ODBC connection string in the 
table properties.  Changing info in the DSN won't take affect until you relink the tables.

-- 
Stuart

On 20 Jun 2011 at 14:53, Lawrence Mrazek wrote:

> Hi Folks:
> 
> I have a quick question regarding a linked ODBC table to SQL Server.
> 
> I inherited an application that uses ODBC to connect to a SQL Server
> DB. I've been able to create new ODBC system DSN's on server1 and
> server2 (they are exactly the same, and connect fine when I test via
> the ODBC control panel). (SQL Server DSN)
> 
> The app works fine when we use linked table manager to establish a
> connection to the ODBC DSN on server1. However, when I move the app to
> server2, it won't connect (I have to completely reconnect the linked
> tables in order for the app to read the ODBC tables).
> 
> Is this behavior by design? That is, when I move an application from
> one machine to another I still have to refresh the linked ODBC tables,
> even though they're hitting against the exact same DSN)?
> 
> Thanks in advance.
> 
> Larry.
> lmrazek at lcm-res.com
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>