This has been discussed at length in the past. (Search the
archives.) Basically, md5 passwords are not supported with the
win32 ODBC driver, and for that matter it does not provide much
security anyway because the connection is not encrypted so all of
the data transferred after logging in securely will be "plain text".
BTW, you may or may not want to look at my method of opening a ODBC
connection in Access (97). It can be a pain to get access/windoze
to use a supplied username/password not give the default ODBC
connection dialog when opening the connection, but I managed to find
a way. (This allows you to make your own custom login form, if this
is important to you). Search google for "odbcrowsource".
HTH
-Cedar
On Tue, 1 Oct 2002, lists wrote:
> I have pgsql 7.2.1 and pgsqlODBC 7.2.1.
>
> The connection fails under these conditions:
>
> Server set up to accept md5 passwords
> ODBC DSN is created without specifying the password at that time
>
> When attempting to use the connection in Access, the pgsql ODBC connection
> dialog is displayed asking for login/pwd; enter it, and you receive:
>
> [ODBC] - connection to '<database>' failed.
>
> The log files seem to indicate that Access is trying to authenticate with
> the Access login and password (by default, login="Admin" and pwd is blank)
> instead of the login/password I supply in the pgsql dialog:
=====
>
> However, the connection works fine under *either* of the following conditions:
>
> I provide the login/password when creating the ODBC DSN
> I change MD5 to "password" at the server.
>
> Any suggestions for getting md5 passwords to work with an interactive Access
> ODBC login? We cannot put the passwords in the DSN, nor can we allow
> unencrypted passwords over the network.
>
> Thanks