Access Error 3151 Oracle
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: MS Access Runtime 2010 ODBC call to run time error 3151 odbc connection failed oracle Oracle not working Microsoft Office > Office 2010 - IT Pro microsoft access error 3151 General Discussions Question 0 Sign in to vote I have a MS Access 2010 applicaton that links ms access error 3151 through an ODBC call to Oracle read data from a table. I have been using this call from MS Access (2000, 2003) to Oracle to read the data
Access Runtime Error 3151
for several years. In Windows XP. When it is run under Windows 7 using the full version of MS Access 2010 using the ODBC connection it works fine. When it is run on another machine under Windows 7 that has only the MS Access 2010 runtime installed through the ODBC connection it returns error 3151 - error 3151 odbc connection failed windows 7 Cannot connect. I tried, ADO as well as DAO with DNS and DNS less connection. No results. Does anybody knows why it does not function under Access 2010 runtime and does function under Access 2010 full version? Thursday, November 03, 2011 7:25 PM Reply | Quote Answers 0 Sign in to vote Hello Jim, It’s still unclear what version of Oracle you are running. FYI, the Microsoft ODBC driver for Oracle was last developed for Oracle 7 and tested for basic functionality against Oracle 8. Beyond those versions you should be using the driver provided by Oracle. Do you receive the same errors when using the Oracle driver with the runtime? I have found that you have another thread discussing this same issue on the msdn forum. http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/620d70f1-5bca-4a51-9afc-10fcba4e866e/ I have discussed this with Sharon and we’ve decided that she will continue working with you on that thread. Please continue your posts on that thread. Regards, Dennis Edited by Dennis Wi - MSFTM
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 error 3151 odbc connection failed ms access Availability Office Add-ins Changelog Microsoft Graph API Office 365 Connectors Office 365
Runtime Error 3151 Odbc Connection Failed Access 2010
REST APIs SharePoint Add-ins Office UI Fabric Submit to the Office Store All Documentation https://www.yammer.com/ http://feeds.feedburner.com/office/fmNx Ask a
Microsoft Visual Basic Runtime Error 3151 Odbc Connection Failed
question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: MS Access Runtime 2010 ODBC call to Oracle not working Microsoft Office https://social.technet.microsoft.com/Forums/office/en-US/8c416503-c07c-4736-b93d-0d7a13ac6a9e/ms-access-runtime-2010-odbc-call-to-oracle-not-working?forum=officeitproprevious for Developers > Access for Developers Question 0 Sign in to vote I have a MS Access 2010 applicaton that links through an ODBC call to Oracle read data from a table. I have been using this call from MS Access (2000, 2003) to Oracle to read the data for several years. In Windows XP. When it is run under Windows https://social.msdn.microsoft.com/Forums/office/en-US/620d70f1-5bca-4a51-9afc-10fcba4e866e/ms-access-runtime-2010-odbc-call-to-oracle-not-working?forum=accessdev 7 using the full version of MS Access 2010 using the ODBC connection it works fine. When it is run on another machine under Windows 7 that has only the MS Access 2010 runtime installed through the ODBC connection it returns error 3151 - Cannot connect. I tried, ADO as well as DAO with DNS and DNS less connection. No results. Does anybody knows why it does not function under Access 2010 runtime and does function under Access 2010 full version? Friday, November 04, 2011 10:43 AM Reply | Quote All replies 0 Sign in to vote Does the connection itself works? Did you test the connection? How do you link the tables to your Oracle database? Also there are differences using 32bit vs. 64bit Windows 7 and Office 2010, if applicable in your situaton. Also put Error handling in place, especially when using Runtime, so you might have better idea what is causing it, see also below thread: http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/aa789d76-d946-4d96-ba0f-71ea2453a6d5/ Hope this helps, Daniel van den Berg | Washington, USA | "Anticipate the difficult by managin
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Getting run-time error 3151 ODBC connection... http://www.sqlservercentral.com/Forums/Topic446169-5-1.aspx 21 posts,Page 1 of 3123»»» Getting run-time error 3151 ODBC connection to ... failed http://www.utteraccess.com/forum/index.php?showtopic=2028787 Rate Topic Display Mode Topic Options Author Message pete.doylepete.doyle Posted Tuesday, January 22, 2008 5:12 PM Forum Newbie Group: General Forum Members Last Login: Monday, January 28, 2008 4:02 PM Points: 8, Visits: 17 Hi - hope someone can help.I've inherited the maintenance and support of a SQL Server 2000 database with an Access 2000 based front-end, running error 3151 on an SBS 2003 server. All worked fine up until yesterday when trying to login using the usual username/password gives the above 3151 error. The line in the VB which generates this is: Set rstRoles = sfdb.OpenRecordset("Roles", dbOpenDynaset, dbSeeChanges)which is opening a simple table of roles to check which level the given user is at. Two things:1 I've noticed the transaction log is huge (12 GB) and had just run out of space error 3151 odbc to grow, but having freed up plenty more disk space, I still get the error2 I can open the database in admin mode and view the tables as normal. Just can't run the front end which the users need.I noticed one post which recommended running the linked tables utlility, which I've done but no difference.Any thoughts or suggestions welcome.:) Post #446169 Minaz AminMinaz Amin Posted Tuesday, January 22, 2008 11:22 PM Mr or Mrs. 500 Group: General Forum Members Last Login: Thursday, September 10, 2015 1:24 AM Points: 580, Visits: 1,750 Is it possible to post the SQL Server error message. Please go to the LOG folder of the SQL Server and read the error log without any extension. "More Green More Oxygen !! Plant a tree today" Post #446246 pete.doylepete.doyle Posted Wednesday, January 23, 2008 12:46 AM Forum Newbie Group: General Forum Members Last Login: Monday, January 28, 2008 4:02 PM Points: 8, Visits: 17 Hi - thanks for the speedy response - I really appreciate it.I've extracted the error message plus the contents of the last 2 error logs into the attached Word document. I can't see anything wrong, but hopefully you might!!ThanksPete Post Attachments SQL Screens.doc (68 views, 106.00 KB) Post #446265 Minaz AminMinaz Amin Posted Wednesday, January 23, 2
Custom Search UtterAccess Forums>Microsoft Access>Access Errors + Error Handling Inconsistent Error 3151, Odbc Connection Failed, Access 2013 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 SebulbaView Member Profile May 20 2015, 04:47 PM Post#1Posts: 18Joined: 2-October 11I am using a pass-through query to get data from an Oracle DB via an ODBC connection. The query, qryD_OraclePeek, has the user credentials hard-coded in the ODBC connection string. The query runs fine from the navigation pane.If I launch the database and open a form that opens a recordset as follows:Dim rst As DAO.RecordsetSet rst = CurrentDb.OpenRecordset("qryD_OraclePeek", dbReadOnly)Access reports the following run-time error:Error Number 3151, ODBC Connection to {ODBC source} failed.However, if I first run the