Access Odbc Error 3151
Contents |
soon) Ruby (coming soon) Getting Started Code Samples Resources Patterns and Practices App Registration Tool Events Podcasts Training API Sandbox Videos Documentation Office Add-ins Office Add-in Availability Office Add-ins Changelog Microsoft Graph API Office 365 Connectors Office 365 REST APIs SharePoint Add-ins Office
Access Error 3151 Odbc Connection To Failed
UI Fabric Submit to the Office Store All Documentation https://www.yammer.com/ http://feeds.feedburner.com/office/fmNx Ask a question Quick access error 3151 odbc connection failed ms access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: ODBC Call Failed - Error 3151 Microsoft Office
Error 3151 Odbc Connection Failed Windows 7
for Developers > Access for Developers Question 0 Sign in to vote We have an Access database migrated from Access 97 to Acces 2007 with some linked tables to an SQL Server 2008 database. We are using a odbc runtime error 3151 File DSN in the ODBC Administrator. Connection tests work fine there. In fact, we have a main form in the Access 2007 application that shows the data always correctly. The problem appears when we execute a task that makes the following call: Dim dbs As Database Dim rstAppend As Recordset Set dbs = CurrentDb Set rstAppend = dbs.OpenRecordset(strAccessTable, dbOpenDynaset, dbSeeChanges) OpenRecordset throws the error number 3151 and occurs randomly but it appears quite frequently. It's sporadic. When we runtime error 3151 odbc connection failed access 2010 don't get the error, the task works fine. It not happens always, mosty we're fine. When it happens it happens for all subsequent tasks tried. We have to close and reopen the Access database and pray to the good Lord that it works. be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 29 Sep 2016 17:05:16 GMT by s_hv972 (squid/3.5.20) here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/5583256/odbc-connection-failed-3151-ms-access-sql-server-2008 more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, http://www.utteraccess.com/forum/runtime-error-3151-odbc-t1966859.html helping each other. Join them; it only takes a minute: Sign up ODBC Connection Failed #3151 MS Access --> SQL Server 2008 up vote 1 down vote favorite I have an MS Access application that links to a error 3151 SQL Server 2008 db for all of its data. For years, it has worked fine when the SQL Server was on Win2008 Standard 64-bit SP2 and SQL Server 2008 v10.0.4. I recently moved the back-end SQL db to a newer server (Win2008 R2 Standard 64-bit and SQL v10.50.1600). After the move, everything on the application worked just fine as expected, no issues. However, we have a month-end process that generates relatively large reports (300-500 pages) which error 3151 odbc uncovered an issue that we don't normally see in our day-to-day processing. My report is based on a pass-through query. The query runs almost instantaneously and produces 8000 rows. I can preview the query and quickly navigate to the end of the RS to see the 8000'th row. No problem. If I pull up the report that's based on that query, I can see that there are 350 pages and I can navigate page-by-page through the report with no problem. I can even type in a page number and jump to page 50, 100, 150, etc. with no problem. Note, there is no processing/code/logic happening on any fired events on the report - just displaying and formatting the data. HERE IS WHERE THE PROBLEM OCCURS: If I preview the report and try to jump to the last page from the first page, it'll sit and think for a while (38 seconds to be exact) and then throw Error #3151 ODBC Connection to [DNS Name] Failed. If I simply update the connect string on the pass-through query to point it back to the "older" SQL Server and run the same thing, it works just fine. I've tried adjusting the connect string to use IP address instead of DNS name, no luck. This is a process that's worked for years with no problem so I know the clien Custom Search UtterAccess Forums>Microsoft® Access>Access Modules Runtime Error 3151: Odbc -- Connection To '{db}' Failed Forum HomeSearchHelpUA Messages|-- UtterAccess.com NewsAccess Knowledge Center|-- Access Code Archive|-- 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 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|-- 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 edarocView Member Profile May 10 2011, 02:40 PM Post#1Posts: 1,025Joined: 27-July 04From: Rochester NY USAI am stuck, have spent almost 2 days trying to resolve this one.nvironment: Access 2007 FE, SQL Server 2008 BE, able to open tables, run queries without getting the error.Development stage - have been working on this project for a few weeks with no problems. Late Friday the