Odbc Call Failed. Error 3146 Timeout
Contents |
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » Microsoft Access » Microsoft Access » ODBC Timout. Error run time error 3146 odbc call failed access 3146 ODBC Timout. Error 3146 Rate Topic Display Mode Topic Options Author Message Chubbly run time error 3146 access GeezerChubbly Geezer Posted Friday, July 29, 2005 10:53 AM Grasshopper Group: General Forum Members Last Login: Tuesday, November 14, 2006 7:19
Run Time Error 3146 Odbc Call Failed Access 2010
AM Points: 21, Visits: 1 I have an Access 2003 databse with tables linked to an SQL back end.I have a piece of code that creates and attempts to open a recordset on one
Access Vba Runtime Error 3146
of these linked tables. However I get ODBC call failed error 3146 or such like.Looping through the errors collection it seems the request has timed out.Any ideas.? Post #205732 Cory PerkinsCory Perkins Posted Saturday, July 30, 2005 9:12 AM SSC-Enthusiastic Group: General Forum Members Last Login: Monday, October 26, 2009 2:56 PM Points: 102, Visits: 6 Would you mind posting the code that creates the recordset? Post #205860 SQLArchSQLArch Posted Monday, August 1, 2005 7:40 AM SSC-Enthusiastic Group: General Forum Members Last Login: Wednesday, May 30, 2012 10:19 PM Points: 184, Visits: 117 You can try increasing ODBC timout for Access query. I think default is 60 secounds by Access. Post #206053 nuno paivanuno paiva Posted Monday, August 1, 2005 7:45 AM Forum Newbie Group: General Forum Members Last Login: Wednesday, August 10, 2005 9:43 AM Points: 8, Visits: 1 hello there,I had to deal with something similar when migrating some ms access apps to sql server...I've just changed the ODBC timeout property in the query designer to 0secs. You can do this programatically also through ADO Hope it helps,Nuno Paiva Post #206058 Chubbly GeezerChubbly Geezer Posted Monday, August 1, 2005 8:17 AM Grasshopper Group: General Forum Members Last Login: Tuesday, November 14, 2006 7:19 AM Points: 21, Visits: 1 Cheers guysbut the problem is when accessing a linked table via code.i.e. linked table = 'subscriptions'code = dim mydb as databaseset mydb = currentdb()dim myrs as recordsetset myrs = mydb.openrecordset("subscriptions")This times out with an ODBC 3146 error. I have also tried accessing the table directly on the server via ADO, but that times out also unless I set the timeout = 0 (which I don't like doing
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Run Time error 3146 ODBC call failed Want to Advertise http://www.sqlservercentral.com/Forums/Topic205732-131-1.aspx Here? Solved Run Time error 3146 ODBC call failed Posted on 2009-02-24 MS Access 2 Verified Solutions 8 Comments 2,298 Views Last Modified: 2012-05-06 Hello, I am trying to call a stored procedure in SQL 2005 from Access 2003 front end. The code is in Access module, and I have macro called AutoExec to https://www.experts-exchange.com/questions/24173950/Run-Time-error-3146-ODBC-call-failed.html run the code when the user opens the database. I am getting the error: "Run-time error 3146 ODBC call failed" password, userid and server are correct. here is my code Option Compare Database Option Explicit Public Function CompareAD2SQL() Dim mydb As Database Dim myq As QueryDef Dim MyText As String Set mydb = CurrentDb() Set myq = mydb.CreateQueryDef("") myq.Connect = "ODBC;DRIVER=SQL;SERVER=;UID=;PWD=;DATABASE=" myq.ReturnsRecords = False mydb.QueryTimeout = 4000 myq.ODBCTimeout = 5000 myq.SQL = "exec dbo.compare" myq.Execute myq.Close mydb.Close End Function - thanks 0 Question by:Harter Facebook Twitter LinkedIn Google Best Solution byHarter it is resolved Go to Solution 8 Comments LVL 28 Overall: Level 28 MS Access 27 Message Expert Comment by:TextReport2009-02-24 Every error you will get will initially be reported as an Error 3146: ODBC Call Failed, you need to improve your error handler to loop through the Errors collection to get the full list of errors. Secondly, try and run the EXEC dbo.compare from a pass t
Custom Search UtterAccess Forums>Microsoft® Access>Access Modules ODBC--call failed Forum HomeSearchHelpUA Messages|-- UtterAccess.com NewsAccess Knowledge Center|-- Access Code Archive|-- http://www.utteraccess.com/forum/ODBC-call-failed-t1332015.html Access Knowledgebase / FAQ|-- Access TutorialsMicrosoft® Access|-- Local Access User Groups (AUGs)|-- Interface Design|-- Access Q and A|-- Access Tables + Relationships|-- Access Queries|-- Access Forms|-- Access Reports|-- Access Macros|-- Access Modules|-- Access Date + Time|-- Access Errors + Error Handling|-- Access Built-in Functions|-- Access Searching + Data Mining|-- Access error 3146 Records|-- Access Security|-- Access Automation|-- Access Database Container|-- Tool bars, Menu bars + Ribbon|-- Access Services (Web Databases)|-- Access Data Access Pages (Deprecated)|-- Access Data Projects - ADP|-- Access Runtime, Packaging & DeploymentAnd More...|-- Microsoft SQL Server|-- SQL Server Reporting Services|-- Microsoft SharePoint|-- Microsoft Internet Explorer|-- Visual Basic 6 and Earlier|-- time error 3146 Visual Basic 2003 and Later|-- ASP and VBScript|-- Web Development|-- PHP, Perl, MySQL and Postgres|-- Other Database Engines|-- BI Tools and Applications|-- JAVA and C#|-- GraphicsMicrosoft® Office|-- Microsoft Excel|-- Microsoft Excel FAQs|-- Microsoft Word|-- Microsoft Outlook|-- Microsoft PowerPoint|-- Microsoft FrontPage/Exp. Web|-- Other Microsoft ProductsPC|-- Network Issues|-- Q & A - Hardware|-- Q & A - Software|-- Q & A - Other PC|-- Virus + Security DiscussionUtterAccess Odds and Ends|-- General Chat|-- Q & A - UtterAccess.com Forums|-- Q & A - Access Wiki Options mattpembView Member Profile Jan 11 2007, 10:56 AM Post#1Posts: 6Joined: 11-January 07I've a strange problem that i can't get to the bottom of. I've designed a query in access and then taken the SQL from that and used it in a module (using an ADODB connection and recordset), something i've done many times. This time when i run the module it almost instantly comes back