sql syntax update problem

[mLipok]

Did you try it ?

 

[faustf]

good day @mLipok

so  i have  a strange  error with  adoo ,  with new version of adoo 

; #INDEX# ========================================================================
; Title .........: ADO.au3
; AutoIt Version : 3.3.10.2++
; Language ......: English
; Description ...: A collection of Function for use with an ADO database like MS SQL, MS Access ...
; Author ........: Chris Lambert, mLipok
; Modified ......: eltorro, Elias Assad Neto, CarlH
; Version .......: 2.1.13 BETA - Work in progress 2016/03/18
; ================================================================================

example , i open a program connect db  , and  after not do nothing  for many  hours , 5 or  8 hours 

when try to work have this  error  (i think exist a time out  for Adoo db ?)

###############################
ADO.au3 v.2.1.13 BETA (1155) : ==> COM Error intercepted !
$oADO_Error.description is:     Unspecified error
$oADO_Error.windescription:     Exception occurred.

$oADO_Error.number is:     80020009
$oADO_Error.lastdllerror is:     0
$oADO_Error.scriptline is:     1155
$oADO_Error.source is:     Provider
$oADO_Error.helpfile is:     
$oADO_Error.helpcontext is:     1240640
###############################
"E:\_GESTIONALE_NEW\GEST_NEW.au3" (566) : ==> Subscript used on non-accessible variable.:
GUICtrlSetData($CONF_Input1, $aRecordsetContent[0][1])
GUICtrlSetData($CONF_Input1, $aRecordsetContent^ ERROR
->09:55:29 AutoIt3.exe ended.rc:1
+>09:55:29 AutoIt3Wrapper Finished.
>Exit code: 1    Time: 4.944e+004
###############################
ADO.au3 v.2.1.13 BETA (1155) : ==> COM Error intercepted !
$oADO_Error.description is:     [MySQL][ODBC 5.3(w) Driver][mysqld-5.6.28]MySQL server has gone away
$oADO_Error.windescription:     Exception occurred.

$oADO_Error.number is:     80020009
$oADO_Error.lastdllerror is:     0
$oADO_Error.scriptline is:     1155
$oADO_Error.source is:     Microsoft OLE DB Provider for ODBC Drivers
$oADO_Error.helpfile is:     
$oADO_Error.helpcontext is:     0
###############################
"E:\_GESTIONALE_NEW\GEST_NEW.au3" (566) : ==> Subscript used on non-accessible variable.:
GUICtrlSetData($CONF_Input1, $aRecordsetContent[0][1])
GUICtrlSetData($CONF_Input1, $aRecordsetContent^ ERROR
->23:34:56 AutoIt3.exe ended.rc:1
+>23:34:56 AutoIt3Wrapper Finished.
>Exit code: 1    Time: 4.914e+004

[mLipok]

Just now, faustf said:

i open a program connect db  , and  after not do nothing  for many  hours , 5 or  8 hours 

when try to work have this  error  (i think exist a time out  for Adoo db ?)

 

Simple answer:   TimeOut

Long answer:
What happend when you come back to your computer - just before you click on mouse or keybord ?
Hibernation ? Sleep ? Power Saving ?
This is your super ECO setting which disables all active connections.

If your connection to DataBase is in realation to any network connection then check your Network Card setting for Power Saving feature and disable it.
Check also all other PowerSaving feature and any eco setting in your system.

If you $oConnection loose connection to DataBase then you need to reconnect.

 

Edited March 21, 2016 by mLipok

[faustf]

ok ok  i  thinked  correct  timeout  

thankz  so much 

 

[mLipok]

Just now, mLipok said:

What happend when you come back to your computer - just before you click on mouse or keybord ?
Hibernation ? Sleep ? Power Saving ?

This is some kind of testing my own knowlegde so I would be happy to know. Can you answer ?

[faustf]

no my pc  is  always on 

never go in standbye or similar the adaper   can go in suspend  but now  i have removed ,  but my  ambient  is  in virtualbox  ,  one  machine  with  server  and  my  develop client ,all  work in localhost  127.0.0.1

 

[mLipok]

Please check again all your ECO system settings, if you change anything then post what you change.
Make new test and back In the morning with news.

 

---

btw.
How about new ADO.au3 version - whether this, solved your previous problems ?

 

---

EDIT:
For future readers: this ECO setting issue with ADO is normal behavior for all types of database, because it is related to how ADO works.

 

Edited March 21, 2016 by mLipok

[faustf]

yea  other  problem is solved  with new  version of  ado 

go  all perfect

 

[mLipok]

Good to know.
With a small steps, we are going to the official release version of ADO.au3.

Thanks for testing and sending feedback.
Feel free to ask if you came in trouble with ADO.

mLipok

 

Edited March 21, 2016 by mLipok

[faustf]

is pleasure  collaborate