X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 12CE852832;
	Sun,  5 Jun 2005 07:53:17 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 26541-03; Sun,  5 Jun 2005 10:53:11 +0000 (GMT)
Received: from ls405.htnet.hr (ls405.htnet.hr [195.29.150.97])
	by svr1.postgresql.org (Postfix) with ESMTP id 1ECDF52817;
	Sun,  5 Jun 2005 07:53:09 -0300 (ADT)
Received: from ls413.t-com.hr (ls413.t-com.hr [195.29.150.237])
	by ls405.htnet.hr (0.0.0/8.12.10) with ESMTP id j55Ar9Eo008344;
	Sun, 5 Jun 2005 12:53:11 +0200
Received: from ls413.t-com.hr (localhost.localdomain [127.0.0.1])
	by ls413.t-com.hr (Qmali) with ESMTP id 4D5F1AC003;
	Sun,  5 Jun 2005 12:53:11 +0200 (CEST)
Received: from zlatkovyfkpgz6 (at05-m287.net.t-com.hr [83.131.117.47])
	by ls413.t-com.hr (Qmali) with SMTP id C47BDEC07C;
	Sun,  5 Jun 2005 12:53:09 +0200 (CEST)
Message-ID: <001501c569bc$c3378150$2f758353@zlatkovyfkpgz6>
From: =?iso-8859-2?Q?Zlatko_Mati=E6?= <zlatko.matic1@sb.t-com.hr>
To: <pgsql-interfaces@postgresql.org>, <pgsql-general@postgresql.org>
Subject: logout Postgres from MS Access (ODBC) ?
Date: Sun, 5 Jun 2005 12:53:08 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0012_01C569CD.85EBEA50"
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.317 tagged_above=0 required=5 tests=AWL, HTML_30_40,
	HTML_MESSAGE, X_MSMAIL_PRIORITY_HIGH, X_PRIORITY_HIGH
X-Spam-Level: 
X-Archive-Number: 200506/216
X-Sequence-Number: 78924

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01C569CD.85EBEA50
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Hi!
In MS Access/PostgreSQL combination I have login form. After user writes =
all neccessary inputs and push the button, a startup procedure creates =
DSN-less=20
connection string, receates all linked tables and change connection =
string in all pass-through queries. It works nice...
But, how to achieve LOGOUT ? I would like to allow users to login/logout =
consecutively from MS Access front-end without need to close front-end.
I tried to perform new login with the same login form after already =
being login, but it seems that Access accepts even wrong passwords after =
connection=20
once established (!?)  It seems that consecutive login does not affect =
at all, after ODBC connection was once established...If you give correct =
username, new DSN-less connection will be accepted even if the password =
is wrong...tabledef.RefreshLink didn't help...
So, I think that  I have to close all ODBC connections (linked tables, =
pass-through queries) somehow and the enforce new login. How to do it ?

Also, I tried to use pg_shadow system table for inspecting whether =
password is OK, but it seems that password is encrypted, so Access can't =
compare password from pg.shadow and password on the login form. What to =
do in order that Access can see actual password from pg_shadow ?

Thanks.=20


------=_NextPart_000_0012_01C569CD.85EBEA50
Content-Type: text/html;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-2">
<META content=3D"MSHTML 6.00.2900.2627" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>Hi!<BR>In MS=20
Access/PostgreSQL combination I have login form. After user writes all=20
neccessary inputs and push the button, a startup procedure creates =
DSN-less=20
<BR>connection string, receates all linked tables and change connection =
string=20
in all pass-through queries. It works nice...<BR>But, how to achieve =
LOGOUT ? I=20
would like to allow users to login/logout consecutively from MS Access =
front-end=20
without need to close front-end.</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>I tried to=20
perform new login with the same login form after already being login, =
but it=20
seems that&nbsp;Access accepts even wrong passwords after connection =
<BR>once=20
established (!?)&nbsp; It seems that consecutive login does not affect =
at all,=20
after ODBC connection was once established...If you give&nbsp;correct =
username,=20
new DSN-less connection will be accepted even if the password is=20
wrong...tabledef.RefreshLink didn't help...<BR>So, I think that&nbsp; I =
have=20
to&nbsp;close all ODBC connections (linked tables, pass-through queries) =
somehow=20
and the enforce new login. How to do it ?</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial =
size=3D2></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>Also, I tried=20
to use pg_shadow system table for inspecting whether password is OK, but =
it=20
seems that&nbsp;password is&nbsp;encrypted, so Access can't compare =
password=20
from pg.shadow and password on the login form. What to do in order that =
Access=20
can see actual password from pg_shadow ?</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3><BR>Thanks.=20
</FONT><BR><BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_0012_01C569CD.85EBEA50--