I was actually thinking DSN - you need api code to change the dsn from
VBA. From the days when I used ODBC tables I undid the dsn then
reconnected the dsn. Can't remember what the deal was because I
switched over to ADO for dealing with sql server tables on the backend
several years ago (mostly for ADP's).
Of the advantages of ADO over ODBC - mostly it is just more flexible and
it is also a disconnected system where ODBC has a continuous connection.
Although, you can certainly run pretty much all the queries through ODBC
that you can run through ADO.
Another feature of ADO is that if someone decides to step up to ADO.Net
the transition is a little easier if the person has experience with
classic ADO (the ADO for Access) because the fundamentals are similar -
Just ADO.Net extends classic ADO about 1000+%
Rich
*** Sent via Developersdex
http://www.developersdex.com ***