Our IP addressed recently changed on our server. When I
put the new IP address in the ODBC outside of Acces, my
access database still cannot connect to the database. Do
I need to change or update in access itself to see the
new IP address?
Thanks
Steve
I recently had the same problem. From what I can see access only uses the dsn
information when the tables are first 'linked'. The servername, schema, etc are
cast in stone at that point. Changing the odbc settings will not redirect
access to use the new info. You have a choice. Write some code that will alter
the table references. (I haven't actually tried this but it would probably work)
or delete and relink the tables once the new odbc reference is in place. It
sucks, but the MS weenies tell me 'all is well and as it should be' so I feel
much better now. I now use a bit of code to set up the connections for all my
linked table references. When the mdb is opened the links are deleted then
reestablished via a local table of tablenames. It causes a considerable delay in
openning the mdb but it clears up the 'linked' table issue. You can see the
problem by unhiding the system tables and looking at MsysObjects. As you will
see the connection info in your tables is locked into the old server address.
deleting and relinking will refresh the connection data and point you to the new
server. (no_ you can't edit this table directly)
I would also suggest switching over to dsnless connections. It has the advantage
of letting multiple uses access the linked tables without needing to set up a
dsn reference for each machine/user.
