RE: odbc driver comunication link failure

["Malchow, Grizzly" <GMalchow@xxxxxxxxxxxxxxxxxxxxx>]

If you are using ADO you can set the connectiontimeout property.
Something like this.
With cn
    .ConnectionString = "DRIVER=Client Access ODBC Driver (32-bit);
SYSTEM=xxxxxxx; DBQ=XXXX; UID=xxxxxxx; PWD=xxxxxx;"
    .ConnectionTimeout = 5
    .CursorLocation = adUseServer
    .Open
End With

This will set the connection time out to 5 minutes

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Angela Wawrzaszek
Sent: Friday, March 25, 2005 7:11 AM
To: midrange-L@xxxxxxxxxxxx
Subject: odbc driver comunication link failure

Hi all,

 

We are running a VB app that connects to the iseries to verify data and
update data.   Everything works fine unless the app is idle for 20-25
minutes,  then the app gets a runtime error   2147467259.   Which is
stating that the ibm iseries access odbc driver communication link
failure,  comm. Re=10054   iseries server disconnection. 

 

Looking this error up it appeared that we needed to change a parm on the
odbc driver to SQL_DRIVER_NOPROMPT.  However it is still occurring.   Is
there a timeout setting on the odbc somewhere that would disconnect on
an idle connection?   Any ideas on anything else or what to do to stop
this?

 

Thankyou,

 

Angela Wawrzaszek

IT Supervisor

Nucor Steel Auburn

(315) 258-4205

awawrzaszek@xxxxxxxxxxxxxxx

 

-- 

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.