After 2 ODBC Connections, connection failes forever

Hi,
I had a C# .NET application that connected to SQL Server with ADO.NET.
All went well.
Then, I had to change the connection to an ODBC connection (to be able
to later connect to another type of db, too).
When I start my app, the app connects twices through ODBC with the SQL
Server -
without problems, twice open and close.
>From the 3rd time onwards, the connection fails with the exception:
"ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Serve
r]Login
failed for user 'OmegaStats'."
This doesn't make any sense. The authenthication went okay twice, but
from the 3rd time onwards, it doesn't work anymore....?!!
Does anyone have any clue what this could be?
Thanks,
JoanI'd follow the clue given in the error message, and use a tool like osql.exe
or Query Analyzer to connect to the SQL instance with that user and its
password to verify if the password was somehow changed.
Linchi
"Joan" wrote:

> Hi,
> I had a C# .NET application that connected to SQL Server with ADO.NET.
> All went well.
> Then, I had to change the connection to an ODBC connection (to be able
> to later connect to another type of db, too).
> When I start my app, the app connects twices through ODBC with the SQL
> Server -
> without problems, twice open and close.
> "ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Ser
ver]Login
> failed for user 'OmegaStats'."
> This doesn't make any sense. The authenthication went okay twice, but
> from the 3rd time onwards, it doesn't work anymore....?!!
> Does anyone have any clue what this could be?
> Thanks,
> Joan
>|||Indeed, after startup an odbc connection string is created including
the password. Upon the 3rd connection, the password has mysteriously
disappeared from the connection string. Why?
Thanks,
Joan