Ummm... a little caution here. Don't get comfortable assuming that ODBC is a dependable measure of how to access a data base. As is typical of Micro$oft, and many other companies which have grown too large and self-important, they have changed the rules. ODBC, having become an industry quasi-standard, is now obsoleted by ADO, the latest in a long series of Microsoft "standards" for database access. One of the best things about ADO, I.M.H.O., is that it does NOT use DSNs or registry entries.
The Python dbapi module for odbc on Windows(r) has not been maintained for years and is acknowledged as buggy. The alternative (sorry, Mark) is a commercial product and therefore not usable for many of us. Adodbapi is my solution of choice. --- Vernon Cole -----Original Message----- ... > DSNs (Data Source Names) are registry keys. The entry for that key > contains among other things the id of the ODBC driver. The string for a > connect contains the DSN (which is evaluated by the driver manager) and > additional connect properties (which are passed to the driver). This at > least was the general idea, which has probably been bended since. The format of ODBC connection strings (sometimes called DSN string or just DSN) goes like this: ... (taken from http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/ht m/odbcsqldriverconnect.asp; At the very least you have to provide the DSN=<name> part of the connection string. All other parts are optional. _______________________________________________ DB-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/db-sig
