Re: SQL ODBC Timer

[MWalter@xxxxxxxxxxxxxxx]

The timeout is the CommandTimeout property of the Connection object. You
can change it in code like this:

cn.Open "Provider=MSDASQL.1;Persist Security Info=False;Data
Source=Orderentry;Mode=ReadWrite"
cn.CommandTimeout = 120



Thanks,

Mark


Mark Walter
Sr. Programmer/Analyst
Hanover Wire Cloth a div of CCX, Inc.
mwalter@hanoverwire.com
http://www.hanoverwire.com
717.637.3795 Ext.3040



                    "Michael Naughton"
                    <mnaughton@juddwire        To:     midrange-l@midrange.com
                    .com>                      cc:
                    Sent by:                   Subject:     SQL ODBC Timer
                    midrange-l-admin@mi
                    drange.com


                    10/30/2002 10:18 AM
                    Please respond to
                    midrange-l






Hi everyone,

I've got a Visual Basic program that connects to my AS/400 data using the
Client Access ODBC driver. The users get to essentially build their own
query by choosing from a list of options and then the program runs an SQL
statement to return the results.

Sometimes, they get a message saying that the CA ODBC time limit of 30 has
been exceeded, and the query doesn't run. I've been able to fix this so
far by building LFs over the files being used, but I'm curious -- does
anyone know where this time limit comes from and (more importantly)
whether it can be changed? If it _can_ be changed, are there any
suggestions (beyond trial and error) for deciding what an appropriate
value should be?

TIA,

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com

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