Odbc 3146 Error
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: error 3146 odbc call failed access 2010 click the register link above to proceed. To start viewing messages, select run time error 3146 odbc call failed access 2010 the forum that you want to visit from the selection below. Results 1 to 5 of 5 Thread: ODBC run time error 3146 odbc call failed oracle - Connection Failed Error 3146 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded access macro error 3146 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, 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
Run Time Error 3146 Odbc Call Failed Mysql
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 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 normal
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 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 http://www.dbforums.com/showthread.php?1642114-ODBC-Connection-Failed-Error-3146 them; it only takes a minute: Sign up Determine real cause 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 http://stackoverflow.com/questions/730414/determine-real-cause-of-odbc-failure-error-3146-with-ms-access tell, this is just a generic ODBC call failed error. I've tried sticking some error handling in 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 J
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 https://www.experts-exchange.com/questions/28562402/How-should-I-troubleshoot-an-ODBC-3146-error-generated-when-VBA-code-is-running-on-a-SQL-Server-backend.html Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > How should I troubleshoot an ODBC 3146 error generated when VBA code is running on a SQL Server backend? Want to Advertise Here? Solved How should I troubleshoot an ODBC 3146 error generated when VBA code is running on a SQL Server backend? Posted on 2014-11-14 MS Access MS SQL error 3146 Server 2008 Windows Networking 7 Verified Solutions 25 Comments 125 Views Last Modified: 2016-02-24 Server: Windows Server 2008 MSS: SQL Server Standard 2008 VBA: 6.5 Front-end: MS Access 2007 Connects to SQL Server tables via Linked Table Manager Hardware: ESX server (virtual environment) I have some simple VBA code on a Windows 2008 server that has been running unchanged since 2005. In the past several months, I have started error 3146 odbc intermittently receiving ODBC 3146 errors in the middle of its processing. It connects to the db, runs through the logic for a number of rows, then errors. The logic path where it fails is identical to the statements where it has successfully processed previous records. ODBC connectivity is not defaulted - connection information is in a table. I have done what I know to troubleshoot it and can use some additional ideas. Code is triggered via Task Scheduler nightly at 11pm. Most nights it runs fine. But occasionally (although frequency seems to be increasing) I come in the next day and Access is sitting with an ODBC 3146 error. I manually kick off the task at that point, and it runs fine. Input is a text file and output is a single SQL Server table. It updates, inserts, deletes from the table based on a condition. Each time I've checked, it is right in the middle of processing where I can see some rows have been updated and can identify where it died. Due to the reasons below (some simply summarized from my description above), it does not appear to be a code or odbc connectivity issue. I will thereby spare details, though I am open to provide them if necessary. * The task has been runni