SQLitening Support Forum

There is a default time-out of 30 seconds on the TCP Send/Recv.  This means
if you do a slExe or slSel and there is no response from the server in 30
seconds then error -18 is raised (%SQLitening_SendOrReceiveError).  Your
vacuum is taking longer then the default 30 seconds so you will have to
increase this time-out time when you do slConnect using the T ModChar or
consider running the vacuum at the server in local mode(check out
SQLiteningServerMonitor -- it was designed for this type of thing). 

Doc about T ModChar in slConnect:

Quote'      Tn = Where n is the how long a TCP SEND/ RECV should
'           wait for completion, in milliseconds (mSec). The
'           default timeout is 30000 milliseconds (30 seconds).
'           This wait should be set to be at least 3 times as
'           long as the wait for a database lock which that
'           default is 10000 milliseconds (10 seconds) and is
'           set in slOpen and can be changed in slSetProcessMods.

Like all slExe commands, it won't return until finished.

The following program runs without problem using the LocalHost server.  Can you post a working program that fails using the LocalHost server?
#Compile Exe
#Include "SQLitening.Inc"
Function PbMain()
   slConnect
   slOpen "sample.db3"
   slSel "Select count(*) from Parts"
   slGetRow
   ?"First Connect Count=" & slF(1)
   slDisconnect
   slConnect
   slOpen "sample.db3"
   slSel "Select count(*) from Parts"
   slGetRow
   ?"Second Connect Count=" & slF(1)
   ?"Main Done
End Function

QuoteMy second thought, since the above doesn't  seem work, is to possibly load the entire database into an array and use the data from there.

That's what slSelAry is for.

slGetChangeCount with the "T" modchar will return total chages since slOpen so somthing like this should work.   Local llChangeCount as Long
   llChangeCount = slGetChangeCount("T")
   slExe "Update T1 Set F1='3x' Where Rowid<3; Update T1 Set F1='x' Where Rowid=1;Update T1 Set F1='3x' Where Rowid<3"
   llChangeCount = slGetChangeCount("T") - llChangeCount
llChangeCount should contain 5 which is the total rows changed by all the statements in the slExe

QuoteWhat version of PB is the DLL compiled in?

Version 10

I have posted fixes (version 1.60.4) for the array scan problem here:

http://www.sqlitening.com/support/index.php?topic=3468.msg17879#msg17879

Fixed all the array scan commands so they would not execute when the array is not dimensioned.

            Tis attachment only contains the changed modules!

Can't explain it.  Some condition is being set-up when using array scan on "empty" array. As you determined only happens when using thread.  Even more strange is to do the msgbox twice, the second will be OK.
    MSGBOX STR$(MyCounter),%MB_SYSTEMMODAL
    MSGBOX STR$(MyCounter),%MB_SYSTEMMODALWhy --- I don't know!

I agree with your fix, the next release will contain the following check:  if ubound(thaSets) = -1 then exit sub              ' Its empty so exit

I will try to add an option to the slConnect which will log the external IP Address.  This feature, if feasible, would be in next release.

Are you requesting that slConnect also pass the External IP Address so it can be logged at server?  Now only the Internal IP Address is passed.

QuoteI am using a password to connect. What about you?

Don't understand, there is no password associated with slConnect.

I installed SQLiteningServer on my wife's laptop(192.168.1.20). Used my desktop as the client(192.168.1.21).
Did the following 20 connects and disconnects without error.  See log below.

   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect
   slConnect "192.168.1.20"
   slDisconnect

Quote
121104132510 Admn Strt ==========<[ Start Server 1.60 ]>==========
121104132510 Admn Flgs TrimLogManually=No
121104132510 Admn Flgs LogConnDcon=Yes
121104132510 Admn Flgs LogInvalidInMessage=Yes
121104132510 Admn Flgs CreateDatabaseAllowed=Yes
121104132510 Admn Data MaxChunkSize=500
121104132510 Admn Data MaxConnections=0
121104132510 Admn Data ConnectionTimeout=30
121104132510 Admn FACT Loaded
121104132510 Host 192.168.1.20(192.168.1.20)  Socket=516  Port=51234  ServiceNameSuffix=
121104142144 Conn #62 SK 516 FredMEIERDESKTOP192.168.1.21
121104142144 Dcon #62 Disconnected
121104142144 Conn #63 SK 516 FredMEIERDESKTOP192.168.1.21
121104142144 Dcon #63 Disconnected
121104142144 Conn #64 SK 516 FredMEIERDESKTOP192.168.1.21
121104142144 Dcon #64 Disconnected
121104142144 Conn #65 SK 516 FredMEIERDESKTOP192.168.1.21
121104142144 Dcon #65 Disconnected
121104142145 Conn #66 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #66 Disconnected
121104142145 Conn #67 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #67 Disconnected
121104142145 Conn #68 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #68 Disconnected
121104142145 Conn #69 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #69 Disconnected
121104142145 Conn #70 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #70 Disconnected
121104142145 Conn #71 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #71 Disconnected
121104142145 Conn #72 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #72 Disconnected
121104142145 Conn #73 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #73 Disconnected
121104142145 Conn #74 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #74 Disconnected
121104142145 Conn #75 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #75 Disconnected
121104142145 Conn #76 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #76 Disconnected
121104142145 Conn #77 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #77 Disconnected
121104142145 Conn #78 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #78 Disconnected
121104142145 Conn #79 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #79 Disconnected
121104142145 Conn #80 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #80 Disconnected
121104142145 Conn #81 SK 516 FredMEIERDESKTOP192.168.1.21
121104142145 Dcon #81 Disconnected

I am using remote mode with a "Local Host" as the server.  This means the server and client are on same computer.  I do all development and testing this way.

I can't cause failure using local host.  Don't see anything in code that would cause problem.  Have you tried a simple connect-disconnect-connect?

   slConnect
   slDisconnect
   slConnect