When an application uses a DSN to connect to a database, but the DSN does not contain enough information to make a connection, the Teradata Database ODBC Driver 17.20 Connection Dialog appears. The most common reason for the Connection Dialog to appear is when the DSN entry has no password saved.
Starting with ODBC Driver for Teradata 17.00, newly created DSNs will not contain a password (see Security Considerations). DSNs created with an older version may have a password saved in the DSN but ODBC Driver for Teradata ignores any passwords stored in a DSN.
If the following dialog appears, complete the required fields and save your changes.