Error Number 3151 Ms-access
Contents |
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 error 3151 odbc connection failed ms access About Us Learn more about Stack Overflow the company Business Learn more about microsoft access error 3151 hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss odbc - connection to name failed. (error 3151) Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ODBC Call Failed - runtime error 3151 odbc connection failed access 2010 Error 3151 up vote 3 down vote favorite 1 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 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
Run Time Error 3151 Odbc Connection Failed Oracle
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 don't get the error, the task works fine. It not happens always, mostly 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. Sometimes, refreshing the tables in the Linked Table Manager solves the problem, but others don't. We receive sometimes an error "ODBC--Call Failed" when refreshing the Linked Table Manager. Deleting the File DSN and creating a new one solves the problem. We have tried with two different drivers (SQL Server and SQL Server Native Client 10) and in both cases the problem remains. Also we have tried to put the Access File in the same machine than the SQL Server and the problem remains. We have increased the ODBC Timeout for all the querys from 60 to 180 seconds,but the problem still
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 08:59:24 GMT by s_wx1131 (squid/3.5.20)
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs 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 Oracle not working Microsoft Office > https://social.technet.microsoft.com/Forums/en-US/8c416503-c07c-4736-b93d-0d7a13ac6a9e/ms-access-runtime-2010-odbc-call-to-oracle-not-working?forum=officeitproprevious Office 2010 - IT Pro General Discussions Question 0 Sign in to vote http://www.sqlservercentral.com/Forums/Topic446169-5-1.aspx 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 7 using error 3151 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 error 3151 odbc 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 - MSFTMicrosoft employee Friday, November 18, 2011 3:08 PM Marked as answer by Rex ZhangModerator Wednesday, December 07, 2011 2:19 AM Friday, November 18, 2011 3:07 PM Reply | Quote All replies 0 Sign in to vote Hello factsjim, Thank you for your post. This is a
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... 21 posts,Page 1 of 3123»»» Getting run-time error 3151 ODBC connection to ... failed 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 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 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