Re: Help: inappropriate OLEDB timeout:
- From: "Matt Neerincx [MSFT]" <mattn@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 18 Sep 2005 23:18:25 -0700
ODBC does not have a way to set this in the datasource, the calling program
has to set this. You ODBC driver may have a way to set a default but most
don't.
--
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Erland Sommarskog" <esquel@xxxxxxxxxxxxx> wrote in message
news:Xns96D1F1A4354FDYazorman@xxxxxxxxxxxx
> Pat (Pat@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
>> Can I change the CommandTimeout via the ODBC admin or regedit or can it
>> only be chaned in program code. I have this problem with MS Access as
>> well.
>
> If you are using ODBC and want to know how to change the timeout for ODBC
> you may want to ask in an ODBC forum.
>
> For ADO, I don't think this can be changed in any other way that by
> changing CommantTimeout on the connection object.
>
> Whether Access has any options for this, I don't know. You should
> ask in Access forum about this.
>
>
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
>
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
>
.
- References:
- Re: Help: inappropriate OLEDB timeout:
- From: Erland Sommarskog
- Re: Help: inappropriate OLEDB timeout:
- Prev by Date: PostgreSQL and OLEDB
- Next by Date: Re: Access Linked server generates (Error 7399) - Help!
- Previous by thread: Re: Help: inappropriate OLEDB timeout:
- Next by thread: PostgreSQL and OLEDB
- Index(es):
Relevant Pages
|
|
