Ms Access Error Number 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 forum that you want to visit from the
Error 3146 Odbc Call Failed
selection below. Results 1 to 5 of 5 Thread: ODBC - Connection Failed Error 3146 Tweet run time error 3146 odbc call failed access 2010 Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded
Run Time Error 3146 Odbc Call Failed Oracle
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 access macro error 3146 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 arises. I turned on the tracing and saw that the SetConnection Attr failed error in the log. Any help is highly appreciated. run time error 3146 odbc call failed mysql 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 Quote 05-07-09,11:42 #3 shanmugha View Profile View Forum Posts Registered User Join Date May 2009 Posts 8 Connecion Failed Error Thanks for your insight.Got the error fixed. The ODBC Connect Str property of the pass thru query which the combobox was using wasnt set to th
Social Groups Pictures & Albums Members List Calendar Search Forums Show Threads Show Posts Tag Search Advanced Search Find All Thanked Posts Go to Page... Thread Tools Rating: Display Modes 04-03-2008, 04:39 AM #1 oumahexi Free Range Witch Join Date: Aug 2006 Location: Brig O'doon Posts: 1,991 Thanks: 4 Thanked 2 Times in 2 Posts ODBC 3146 Error for Some Users Hello again My apologies for another posting so soon after the last. My problem is an inherited database that just does not behave. The latest error is the ODBC 3146 (Error occurred report could not be checked). This error occurs when a user tries to run a http://www.dbforums.com/showthread.php?1642114-ODBC-Connection-Failed-Error-3146 report. Our system collects data via Access 2002 into fields that are linked to SQL Server 2000, the information is then passed back into Access to run the required reports. The reason for this is that the original database relied on Access information being fed in from an external source. The source changed to SQL while our database was in it's infancy, but management decided that rather than rebuild from scratch it would be best to http://www.access-programmers.co.uk/forums/showthread.php?t=146862 patch the old system up I know there are many queries in the database which query a query for no apparent reason - example: qryThisQuery interrogates qry_tblThisQuery (selecting all fields from this query), qry_tblThisQuery interrogates dbotblThisQuery (selecting all fields from the table). My first thought about the ODBC errors being experienced is that there are too many scenarios like this and it limits the efficiency of the database. However, my hands are tied, I am only permitted to patch it up. My second thought is that perhaps the user needs her registry cleaned out? or perhaps there may be too much junk in her temp folder? The big problem is that it works on my pc and another user's pc but not on the third. any thoughts? Very much appreciated. Thanks Ouma oumahexi View Public Profile Visit oumahexi's homepage! Find More Posts by oumahexi 04-03-2008, 04:42 AM #2 Rabbie Super Moderator Join Date: Jul 2007 Location: In Exile in Wiltshire Posts: 5,892 Thanks: 106 Thanked 72 Times in 64 Posts My first reaction when it works on some PCs but not on others is to check the route to the SQL Server DB from the failing PC. Is it the same as on the working ones. Good luck __________________ The best solution is the simplest one that meets all
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 http://stackoverflow.com/questions/730414/determine-real-cause-of-odbc-failure-error-3146-with-ms-access 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 of ODBC failure (error 3146) with error 3146 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 the VB script that is launching the reports, but error 3146 odbc 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 Update_Temp() On Error GoTo ErrorTrap ' Execute connect code at this point Exit_errortrap: Exit Sub ErrorTrap: Dim my