Thank you for your answer

Well - "sleeping" is a process-state where the thread is waiting for
the client to send a new command to it. You can monitor it in
MySqlAdmin processlist.

Beside this sleeping process I have no problems connecting through
odbc. MySQL Connector/ODBC works fine.

And as I said - using same connection/odbc etc. from an ordinary
application does not create these sleeping processes.



"Alvin Bruney" <vapordan_spam_me_not@hotmail_no_spamhotmail.com > wrote in message news:<uZC2E5MUDHA.2020@TK2MSFTNGP11.phx.gbl>...
> i'm lost by this. what is a sleeping process?
>
> you say you are using mysql yet you are connecting thru odbc. Mysql has it's
> own .net providers. you should be connecting like this
> MySQLConnection cn = new MySQLConnection(MyConString);
>
> these types are imported into the namespace after setting a reference to
> sharpziplib and bytefx.data assemblies. finally you would need to import
> ByteFX.Data.MySQLClient into your application in the using or imports
> section depending on whether you are using c # or vb.net
>
> "jan nielsen" <nettet@jubiimail.dk> wrote in message
> news:79cc6d01.0307221325.a0913c7@posting.google.co m...
> > Hi
> >
> > Whenever I connect (successfully) to MySql from asp.net it creates a
> > sleeping process.
> >
> > This simple connection in an asp.net-page:
> >
> > OdbcConnection MyConnection = new OdbcConnection(MyConString);
> > MyConnection.Open();
> >
> > Label1.Text = "!!! success !!!";
> > MyConnection.Close();
> >
> > creates a sleeping process - while the same connection in an ordinary
> > c# .exe-application does not!!
> >
> > I'm using Microsoft.Data.Odbc.
> >
> > Am I doing something wrong?, or Microsoft? or is this the way it is
> > meant to be?
> >
> > Jan Nielsen