I have had similar problems caused by Firewall software. The MYSQL server Had a firewall program that decided that a lot of calls to the server was a threat and shut down the connection for several minutes.

This was temporally fixed by shutting down the fire wall software, and then latter setting up the firewall with rules to allow MYSQL traffic. Later testing found my creating a Connection object , opening it and then passing the open connection to the command object when creating it seemed to remedy the issue. It seems to be caused by using a closed connection and having the connection continually opened and closed.

I quite successfully use a generic data connection (data.idbdataconnection) assigning it to a provider at run time. Use it to crate data and command objects and open connection prior to a series of commands.

Because our data programs can use multiple data sources eg. MySQL, MSSQL, access ... I create the dataconnection in a generic DLL which them passes out a dataconnection of the correct type here is some sample code .

Function GetDataConnection(ConnectionType as Integer,ConnectionString as String)as IDBDataConnection

Select Case ConnectionType Case 1 Dim MYSQL as New MYSQLConnection ... set up connection return MYSQL Case 2 Dim ODBC as new Data.ODBCConnection ... set up connection return ODBC End Select

End Function

I then create what ever data object I need and use the System wide Data Connection then the code all flows nicely.

'Open Data Connection IF DBDataConnection.State = CLOSED then DBDataConnection.Open END IF

.... Process Data

DBDataConnection.Close

Hope it helps some one.

Regards, Justin Elward

Blue Wave Software Pty Limited jus...@bluewavesoftware.com.au

Ph. +61 2 4320 6090 (Central Coast - Office) Ph. +61 2 4915 7064 (Newcastle) Ph. +61 2 8208 5982 (Sydney)

Fx. +61 2 4320 6092

----------------------------------------------------------------------------

------------------- DISCLAIMER: This message is proprietary to Blue Wave Software Pty Limited (BWS) and is intended solely for the use of the individual or individuals to whom it is addressed. It may contain privileged or confidential information and should not be circulated with out informing BWS prior or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. BWS accepts no responsibility (except where required under Australian law) for loss or damage arising from the use or misuse of the information transmitted by this email including damage from virus."

----------------------------------------------------------------------------

-------------------