3146 Access Error
Contents |
One games Xbox 360 games PC access error 3146 odbc call failed games Windows games Windows phone games Entertainment All access error 2950 Entertainment Movies & TV Music Business & Education Business Students & ms access error 3146 odbc call failed educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
Access Runtime Error 3146
Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft access macro error 3146 Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
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: error 3146 odbc call failed access 2010 Display Modes 04-03-2008, 04:39 AM #1 oumahexi Free Range Witch
Run Time Error 3146 Odbc Call Failed Access 2010
Join Date: Aug 2006 Location: Brig O'doon Posts: 1,991 Thanks: 4 Thanked 2 Times in 2 Posts ODBC 3146 Error
Run Time Error 3146 Odbc Call Failed Oracle
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 https://support.microsoft.com/en-us/kb/161288 occurred report could not be checked). This error occurs when a user tries to run a 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 http://www.access-programmers.co.uk/forums/showthread.php?t=146862 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 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,891 Thanks: 106 Thanked 72 Times in 64 P
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 https://bytes.com/topic/access/answers/206736-odbc-call-error-3146-a 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 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 4,97622862 asked Apr 8 '09 at 14:57 Aaron Hinni 10.9k33134 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 mye
question and get tips & solutions from a community of 418,417 IT Pros & Developers. It's quick & easy. ODBC Call error 3146 P: n/a Jimbo I have an access 97 database linked to sql server..I click update on a form and get an error message: Run-time error 3146 ODBC call failed The debugger points to this line: MyTable.Update In this segment of code: Private Sub Update5_Click() Dim MyDB As Database, MyTable As Recordset, MyTmpTable As Recordset, Criteria As String, NewID As Long Set MyDB = DBEngine.Workspaces(0).Databases(0) Set MyTable = MyDB.OpenRecordset("Dx5", DB_OPEN_DYNASET, dbSeeChanges) Set MyTmpTable = MyDB.OpenRecordset("tmp_RockDx5", DB_OPEN_DYNASET) MyTable.AddNew MyTable.Update MyTable.Move 0, MyTable.LastModified NewID = MyTable![Dx5ID] Me![HoldNewDxID] = NewID If DCount("*", "Dx5Current") > 0 Then Me![HoldOldDxID] = Me![Dx5Current].Form![Dx5ID] 'Put end date on the current Axis 5 'record Me![Dx5Current].Form![EndDate] = Date DoCmd.DoMenuItem A_FORMBAR, A_FILE, A_SAVERECORD 'Copy in data from the current Axis 5 'record to the new record, since it is 'likely to be similar Set MyTable = MyDB.OpenRecordset("Dx5", DB_OPEN_DYNASET) holdnum = Forms![DxSummary]![HoldNewDxID] Criteria = "[Dx5ID] = " & holdnum MyTable.FindFirst Criteria MyTable.Edit MyTable![CurrentGAF] = Me![Dx5Current].Form![CurrentGAF] MyTable![HighestGAFLastYear] = Me![Dx5Current].Form![HighestGAFLastYear] MyTable.Update End If Me.Visible = False Me![Dx5Current].Requery 'This is necessary in order to release the 'record, so that it can be edited if the 'user uses the Cancel button on the add-edit 'form Criteria = "[Dx5ID] = Forms![DxSummary]![HoldNewDxID]" DoCmd.OpenForm "AddDx5", , , Criteria, A_EDIT MyTmpTable.Close MyTable.Close Forms![AddDx5]![ClientID] = Forms![LogIn]![ActiveClient] Forms![AddDx5]![StaffID] = Forms![LogIn]![ActiveStaff] End Sub Nov 13 '05 #1 Post Reply Share this Question 2 Replies P: n/a Steve Jorgensen Since you are getting an ODBC error, I assume you're using linked tables. The ODBC call failed error is the same for -any- server-side failure, and is not terribly informative. To get the useful error information in these cases, you must examine the Errors collection. Looking at what you're doing, though, I'm guessing the table has one or more required fields with no default values, so doing an Update immediately after an AddNew is trying to create a new record without the minimum required field data. On 29 Mar 2005 07:00:05 -0800, "Jimbo"