Msaccess Odbc Error 3146
Contents |
your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the run time error 3146 odbc call failed access forum that you want to visit from the selection below. Results 1 to 5 of
Run Time Error 3146 Odbc Call Failed Access 2010
5 Thread: ODBC - Connection Failed Error 3146 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced
Run Time Error 3146 Odbc Call Failed Oracle
Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 05-05-09,19:17 #1 shanmugha View Profile View Forum Posts Registered User Join Date May 2009 Posts 8 Unanswered: ODBC - Connection Failed Error 3146 Hi,
Access Vba Runtime Error 3146
I have a situation here.I will be glad if anyone could help. We have a Microsoft Access 2003 accessing the SQL Server 2000 database using ODBC connection.I have set the database as a System Datasource with SQL Server driver and the connection settings. When i launch the .mdb application,i am able to connect to the database and fetch results.But only while populating the data on one of the combobox,the ODBC connection failed error 3146 access macro error 3146 arises. I turned on the tracing and saw that the SetConnection Attr failed error in the log. Any help is highly appreciated. Thanks in advance. Reply With Quote 05-05-09,20:24 #2 pkstormy View Profile View Forum Posts Moderator Join Date Dec 2004 Location Madison, WI Posts 3,926 Are you able to enter data for this field directly into the table? If not, are you able to enter data in this field directly into the SQL Server table (I'm guessing yes.) You can also try refreshing (or delete and relink) the linked tables. You can also put in a msgbox me!MyProblemField in the AfterUpdate (or BeforeUpdate) event to see what value is actually being saved in the combobox and see if it matches the SQL Server field type. I'm not sure what the error exactly means but these are some things I normally do to troubleshoot. My guess is that you may not be passing the correct value type for that field (what is the field type defined as on SQL Server?) Or it's a relational problem. Can you explain more on what kind of field type (and what it's for) that is giving you problems? Last edited by pkstormy; 05-05-09 at 20:34. Expert Database Programming MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0) Reply With Qu
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 run time error 3146 odbc call failed mysql About Us Learn more about Stack Overflow the company Business Learn 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 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Determine real cause http://www.dbforums.com/showthread.php?1642114-ODBC-Connection-Failed-Error-3146 of ODBC failure (error 3146) with ms-access? up vote 6 down vote favorite 2 My client is using Access as a front end to a SQL Server database. They recently started getting ODBC - 3146 errors from time to time when running some reports. From what I can tell, this is just a generic ODBC call failed error. I've tried sticking some error handling in http://stackoverflow.com/questions/730414/determine-real-cause-of-odbc-failure-error-3146-with-ms-access the VB script that is launching the reports, but I am not having any luck getting extra error information. Code looks a bit like this. Public Function RunReports() On Error GoTo MyErrorTrap DoCmd.OpenReport "blah", acViewPreview DoCmd.Close DoCmd.OpenReport "foo", acViewPreview DoCmd.Close Exit_function: Exit Function MyErrorTrap: Dim errX As DAO.Error Dim MyError As Error If Errors.Count > 1 'This always seems to be 0, so no help For Each errX In DAO.Errors 'These are empty even if dont check for Errors.Count Debug.Print "ODBC Error" Debug.Print errX.Number Debug.Print errX.Description Next errX Else Debug.Print "VBA Error" Debug.Print Err.Number Debug.Print Err.Description End If 'Also have tried checking DBEngine.Errors, but this is empty too End Function I've also enabled tracing on the ODBC side, but that has bogged things down way too much, and I am so far unable to recreate the ODBC error. I am completely open for suggestions on how to diagnose this. vba ms-access vbscript odbc share|improve this question edited Jun 16 '14 at 20:23 Smandoli 5,00122862 asked Apr 8 '09 at 14:57 Aaron Hinni 11k43134 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote Use the DbEngine.Errors collection. Sub Upd
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 http://stackoverflow.com/questions/20504074/access-odbc-error-3146 site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x https://www.experts-exchange.com/questions/27831438/MS-Access-VB-Runtime-error-3146-ODBC-Call-Failed-connecting-to-mySQL.html Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Access/ODBC error error 3146 3146 up vote 2 down vote favorite I have an MS Access 2007 front end to a MS SQL Server 2008R2 back end. I've got a query that's part of a loop, and it's suddenly started generating Run-time error '3146': ODBC--call failed. errors on one query as the loop itterates. Oddly, it's not the first iteration. EDIT: When I say suddenly, it's been running time error 3146 like this just fine for several months (probably since March). Set db = CurrentDb db.QueryTimeout = 480 'thought there was a timeout issue, so set this very high Set SupvRS = db.OpenRecordset("SELECT DISTINCT tblProcessors.Supervisor, tblProcessors.SupervisorEmail " & _ " FROM tblProcessors INNER JOIN (tblAuditPr INNER JOIN tblAuditPr_A ON tblAuditPr.PrAudit_ID = tblAuditPr_A.PrAudit_ID)" & _ " ON tblProcessors.Processor = tblAuditPr_A.Processor" & _ " WHERE tblProcessors.Supervisor IS NOT NULL " & _ " AND tblAuditPr.EndDate BETWEEN " & GetSQLDate(Me.txtFrom) & " AND " & GetSQLDate(Me.txtTo) & _ " AND tblProcessors.Processor<>'Default Processor' " & _ " AND tblAuditPr_A.Answer Not In ('NA','NF')" & _ " AND tblAuditPr.Status = 'Submitted'") Do While Not SupvRS.EOF 'Send Supervisor Email Attachment = PARG.GenerateAuditReport(SupvRS.Fields("Supervisor"), parSupervisor, Me.txtFrom, Me.txtTo) Set EmailRS = db.OpenRecordset("SELECT * FROM tblProcessors WHERE Supervisor = " & GetSQLString(SupvRS.Fields("Supervisor"))) If EmailRS.EOF Then Err.Raise -234923, Description:="Cannot find tblProcessors record for " & SupvRS.Fields("Supervisor") & "." End If If IsNull(EmailRS.Fields("SupervisorEmail")) Then MailTo =
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 > MS Access (VB) Runtime error 3146 ODBC Call Failed (connecting to mySQL) Want to Advertise Here? Solved MS Access (VB) Runtime error 3146 ODBC Call Failed (connecting to mySQL) Posted on 2012-08-16 MS Access MySQL Server 1 Verified Solution 2 Comments 7,789 Views Last Modified: 2012-08-23 Hi Experts I have recently had to update mySQL from 5.1 to 5.5 with a MS Access 2003 front end (via ODBC links) When I run some legacy SQL queries on Access using a form I inherited (and worked fine before the rebuild) I am getting Visual Basic Error 3146 ODBC Call Failed. I can run the code directly within mySQL so I am at a loss what the problem might be. I have switched ODBC Tracing on, and get the following fragment in the log - which doesnt really help much: InterconnecTRep 90-14f0 EXIT SQLExecDirect with return code -1 (SQL_ERROR) HSTMT 0FA83860 UCHAR * 0x11CF44B4 [ 2010] "## This report currently includes ...(SQL is in here)" SDWORD 2010 DIAG [S1000] [MySQL][ODBC 5.1 Driver][mysqld-5.5.27-log]Query execution was interrupted (1317) Does anyone know how I can force more detail on the 3146 error, so it shows me what the *real* problem is? Thanks 0 Question by:stummj Facebook Twitter LinkedIn Google LVL 56 Active today Best Solution byJim Dettman (Microsoft MVP/ EE MVE) <