logout for ODBC source ?

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
connection string, receates all linked tables and change connection string
in all pass-through queries. It works nice...
But, how to achieve LOGOUT ? How to close all ODBC connections and enforce
new login ?
I tried to perform new login with the same login form after already being
login, but it seems that It accepts even wrong passwords after connection
once established (!?) It seems that consecutive login does not affect at
all after ODBC conncetion once established...
So, how could I close ODBC connection and enforce new login ?
Thanks.

re: logout for ODBC source ?

Zlatko Matiæ wrote:[color=blue]
> 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
> connection string, receates all linked tables and change connection string
> in all pass-through queries. It works nice...
> But, how to achieve LOGOUT ? How to close all ODBC connections and enforce
> new login ?
> I tried to perform new login with the same login form after already being
> login, but it seems that It accepts even wrong passwords after connection
> once established (!?) It seems that consecutive login does not affect at
> all after ODBC conncetion once established...
> So, how could I close ODBC connection and enforce new login ?
> Thanks.[/color]

Wait for MS to fix Access so that it closes ODBC databases when it's
done with them?

--
[OO=00=OO]

re: logout for ODBC source ?

?! :)

"Trevor Best" <nospam@besty.org.uk> je napisao u poruci interesnoj
grupi:429f4ea6$0$24082$db0fefd9@news.zen.co.uk...[color=blue]
> Zlatko Matiæ wrote:[color=green]
>> 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 connection string, receates all linked tables and change
>> connection string in all pass-through queries. It works nice...
>> But, how to achieve LOGOUT ? How to close all ODBC connections and
>> enforce new login ?
>> I tried to perform new login with the same login form after already being
>> login, but it seems that It accepts even wrong passwords after connection
>> once established (!?) It seems that consecutive login does not affect at
>> all after ODBC conncetion once established...
>> So, how could I close ODBC connection and enforce new login ?
>> Thanks.[/color]
>
> Wait for MS to fix Access so that it closes ODBC databases when it's done
> with them?
>
> --
> [OO=00=OO][/color]

re: logout for ODBC source ?

Zlatko Matic wrote:[color=blue]
> ?! :)
>
> "Trevor Best" <nospam@besty.org.uk> je napisao u poruci interesnoj
> grupi:429f4ea6$0$24082$db0fefd9@news.zen.co.uk...
>[color=green]
>>Zlatko Matiæ wrote:
>>[color=darkred]
>>>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 connection string, receates all linked tables and change
>>>connection string in all pass-through queries. It works nice...
>>>But, how to achieve LOGOUT ? How to close all ODBC connections and
>>>enforce new login ?
>>>I tried to perform new login with the same login form after already being
>>>login, but it seems that It accepts even wrong passwords after connection
>>>once established (!?) It seems that consecutive login does not affect at
>>>all after ODBC conncetion once established...
>>>So, how could I close ODBC connection and enforce new login ?
>>>Thanks.[/color]
>>
>>Wait for MS to fix Access so that it closes ODBC databases when it's done
>>with them?[/color][/color]

My experience with SQL Server and ODBC is that I open a database
variable and have linked tables. Everything is closed and db vars set to
nothing before I close the app. If I close the front end MDB from Access
it does not close the connection to SQL Server until I actually exit Access.

If I close and re-open the app without exiting Access and I log in as
another user I have the problem that my app thinks I'm somebody and SQL
Server thinks I'm somebody else.

You can imagine the problem if the server thinks that numpty logged in
ATM is an admin.

--
[OO=00=OO]

re: logout for ODBC source ?

Right!
That bothers me too...


"Trevor Best" <nospam@besty.org.uk> je napisao u poruci interesnoj
grupi:429fa426$0$23699$db0fefd9@news.zen.co.uk...[color=blue]
> Zlatko Matic wrote:[color=green]
>> ?! :)
>>
>> "Trevor Best" <nospam@besty.org.uk> je napisao u poruci interesnoj
>> grupi:429f4ea6$0$24082$db0fefd9@news.zen.co.uk...
>>[color=darkred]
>>>Zlatko Matiæ wrote:
>>>
>>>>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 connection string, receates all linked tables and change
>>>>connection string in all pass-through queries. It works nice...
>>>>But, how to achieve LOGOUT ? How to close all ODBC connections and
>>>>enforce new login ?
>>>>I tried to perform new login with the same login form after already
>>>>being login, but it seems that It accepts even wrong passwords after
>>>>connection once established (!?) It seems that consecutive login does
>>>>not affect at all after ODBC conncetion once established...
>>>>So, how could I close ODBC connection and enforce new login ?
>>>>Thanks.
>>>
>>>Wait for MS to fix Access so that it closes ODBC databases when it's done
>>>with them?[/color][/color]
>
> My experience with SQL Server and ODBC is that I open a database variable
> and have linked tables. Everything is closed and db vars set to nothing
> before I close the app. If I close the front end MDB from Access it does
> not close the connection to SQL Server until I actually exit Access.
>
> If I close and re-open the app without exiting Access and I log in as
> another user I have the problem that my app thinks I'm somebody and SQL
> Server thinks I'm somebody else.
>
> You can imagine the problem if the server thinks that numpty logged in ATM
> is an admin.
>
> --
> [OO=00=OO][/color]

re: logout for ODBC source ?

Zlatko Matiæ wrote:[color=blue]
> 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
> connection string, receates all linked tables and change connection string
> in all pass-through queries. It works nice...
> But, how to achieve LOGOUT ? How to close all ODBC connections and enforce
> new login ?
> I tried to perform new login with the same login form after already being
> login, but it seems that It accepts even wrong passwords after connection
> once established (!?) It seems that consecutive login does not affect at
> all after ODBC conncetion once established...
> So, how could I close ODBC connection and enforce new login ?
> Thanks.[/color]

Are you doing the RefreshLink after you change the Connection? If not,
then the Links are not actually changed in memory. If you are already
doing this then there may not be a solution. I expermented with changing
the connection to invalid values and it errors on the RefreshLink.

--
Bri

re: logout for ODBC source ?

Hi!
No, I haven't used RefreshLink yet....I will try.


"Bri" <not@here.com> je napisao u poruci interesnoj
grupi:Pg0oe.1562597$8l.856396@pd7tw1no...[color=blue]
> Zlatko Matiæ wrote:[color=green]
>> 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 connection string, receates all linked tables and change
>> connection string in all pass-through queries. It works nice...
>> But, how to achieve LOGOUT ? How to close all ODBC connections and
>> enforce new login ?
>> I tried to perform new login with the same login form after already being
>> login, but it seems that It accepts even wrong passwords after connection
>> once established (!?) It seems that consecutive login does not affect at
>> all after ODBC conncetion once established...
>> So, how could I close ODBC connection and enforce new login ?
>> Thanks.[/color]
>
> Are you doing the RefreshLink after you change the Connection? If not,
> then the Links are not actually changed in memory. If you are already
> doing this then there may not be a solution. I expermented with changing
> the connection to invalid values and it errors on the RefreshLink.
>
> --
> Bri
>[/color]

re: logout for ODBC source ?

TableDef.RefreshLink didn't help me.
Bye.

"Bri" <not@here.com> je napisao u poruci interesnoj
grupi:Pg0oe.1562597$8l.856396@pd7tw1no...[color=blue]
> Zlatko Matiæ wrote:[color=green]
>> 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 connection string, receates all linked tables and change
>> connection string in all pass-through queries. It works nice...
>> But, how to achieve LOGOUT ? How to close all ODBC connections and
>> enforce new login ?
>> I tried to perform new login with the same login form after already being
>> login, but it seems that It accepts even wrong passwords after connection
>> once established (!?) It seems that consecutive login does not affect at
>> all after ODBC conncetion once established...
>> So, how could I close ODBC connection and enforce new login ?
>> Thanks.[/color]
>
> Are you doing the RefreshLink after you change the Connection? If not,
> then the Links are not actually changed in memory. If you are already
> doing this then there may not be a solution. I expermented with changing
> the connection to invalid values and it errors on the RefreshLink.
>
> --
> Bri
>[/color]