Groups > comp.databases.ms-sqlserver > #1726

Re: Unable to connect Client to SQL Server

Path	csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.fsmpi.rwth-aachen.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From	Erland Sommarskog <esquel@sommarskog.se>
Newsgroups	comp.databases.ms-sqlserver
Subject	Re: Unable to connect Client to SQL Server
Date	Wed, 12 Mar 2014 23:20:20 +0100
Organization	Erland Sommarskog
Lines	17
Message-ID	<XnsA2EEED6A8C514Yazorman@127.0.0.1> (permalink)
References	<lfit86$thr$1@speranza.aioe.org> <XnsA2EC5B95F23F9Yazorman@127.0.0.1> <lfl1cr$e5b$1@speranza.aioe.org> <XnsA2ECD650A5C8DYazorman@127.0.0.1> <lflktn$1ek$1@speranza.aioe.org> <XnsA2ED645E08739Yazorman@127.0.0.1> <lfn01j$r2$1@speranza.aioe.org> <XnsA2EDD5DCC29C5Yazorman@127.0.0.1> <lfppd5$vev$1@speranza.aioe.org> <XnsA2EEA7FCDF520Yazorman@127.0.0.1> <lfq0to$k69$1@speranza.aioe.org> <lfq31r$q9l$1@speranza.aioe.org> <XnsA2EED87FC9ED2Yazorman@127.0.0.1> <lfqh0r$20d$1@speranza.aioe.org>
Mime-Version	1.0
Content-Type	text/plain; charset=windows-1252
Content-Transfer-Encoding	8bit
Injection-Info	mx05.eternal-september.org; posting-host="fd3d6d0229f14a752f017d8f9903addd"; logging-data="23735"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/9igSNF2O6jBIj0pR3m6Yd"
User-Agent	Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32)
Cancel-Lock	sha1:/5AIDW1uHtQ55E/SGGTZilpBh5s=
Xref	csiph.com comp.databases.ms-sqlserver:1726

Show key headers only | View raw

Bruno Campanini (brunocam@libero.it) writes:
> I don't have any connection string yet, I was operating Access 
> manually.

Well, how you would specify the connection timeout in that case is
an Access question. And I dont't know Access.

> Do you have a connection string I can work around on VBAccess?

"Driver={SQL Server Native Client 11.0};Server=SERVER;UID=User;Database=yourdb;Connect timeout=50"

Although, when I look closer, I realise that Connect timeout is
only listed for OLE DB, not for ODBC. But there must be a connect
timeout somewhere, so try the above.

-- 
Erland Sommarskog, Stockholm, esquel@sommarskog.se

Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Find similar

Thread

Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-10 00:24 +0100
  Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-10 08:00 +0000
    Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-10 19:47 +0100
      Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-10 21:04 +0100
        Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-11 01:21 +0100
          Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-11 08:51 +0000
            Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-11 13:37 +0100
              Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-11 21:01 +0100
                Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 15:02 +0100
                Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-12 15:30 +0000
                Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 17:10 +0100
                Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 17:46 +0100
                Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-12 21:16 +0100
                Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 21:45 +0100
                Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-12 23:20 +0100

csiph-web