Hi..

I do have an app. that was created for remote web access of mysql data..

it is an ussual logic by:

1. open the conection to DB
2. start the update/insert user procedures.. During almost all day long..
3. Close the conection

All working fine, on developing time.. But, on the production, the app. faces the new variable named 'time'..

It is very common for a given period.. the application starts to return -1 on the insert/update sql's commands...

So, at this time, for me, the logic stuff.. seems to change the logic to start the conection again on every -1 returned...

But, before to go to this (a little) unlogic step.. I'd like to read advices here.. Or (who knows) maybe other options on the connections..

TIA

BTW, this is my actual try:

	privStrConexao               = "DRIVER=MySQL ODBC 3.51 Driver;" +;
		"SERVER="                + this.cServidor_bancodedados + ";" +;
		"UID=myuser;"             +;
		"PWD=mypass;"           +;
		"DATABASE=mydb;"  +;
		"WSID=" + Lower(Substr(Sys(0), 1, Atc("#", Sys(0))-1)) + ";" +;
		"Port=3306;OPTION=3;" +;
		"Trusted_Connection=Yes"
	privConexao    				 = 0
	i3             				 = 0
	If  Type("this.privConexao") = "U"
		This.AddProperty("privConexao", .F.)
	Endif
	This.privConexao			 = Sqlstringconnect(privStrConexao)

Claudio