Odbc 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 run time error 3146 odbc call failed access forum that you want to visit from the selection below. Results 1 to 5 of error 3146 access 5 Thread: ODBC - Connection Failed Error 3146 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced
Error 3146 Odbc Call Failed Access 2010
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,
Run Time Error 3146 Odbc Call Failed Access 2010
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 run time error 3146 odbc call failed oracle 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 Quot
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
Access Macro Error 3146
#1 oumahexi Free Range Witch Join Date: Aug 2006 Location: Brig O'doon run time error 3146 odbc call failed mysql 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 http://www.dbforums.com/showthread.php?1642114-ODBC-Connection-Failed-Error-3146 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 changed to SQL while our database was in it's infancy, but management decided that rather than rebuild http://www.access-programmers.co.uk/forums/showthread.php?t=146862 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,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 workin
If this is 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 http://www.vbforums.com/showthread.php?578312-Error-Number-3146-ODBC-call-failed you want to visit from the selection below. Results 1 to 7 of 7 Thread: https://bytes.com/topic/access/answers/206736-odbc-call-error-3146-a Error Number : 3146,ODBC--call failed. Tweet Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Jul 29th, 2009,07:27 AM #1 kirti_sm25 View Profile View Forum Posts Thread Starter New Member Join Date May 2009 Location Gujarat,India Posts 10 Error Number : 3146,ODBC--call failed. Hiee there... I am downloading data error 3146 from sql server 2005 to my access database using the following query in Visual Basic 6.0 HTML Code: CompTemp.Execute "Insert INTO tempnav(abc,xyz,pqr,asd,qwe,rty,dsf) " & _ "Select Distinct abc,xyz,pqr,rep as repur,rate as sale,0,'11/11/1111' " & _ "FROM [ODBC;Driver=SQL Server;SERVER=mysqlserver;DATABASE=mysqldatabase;UID=ServerSQLuserid;PWD=ServerSQLpaswd;].[myTableName] " -Here TempNav is my Local Access Database -CompTemp is DAO database connection This query works perfectly through out, but if once my internet connection is lost then this query continously gives ODBC call Failed error although my error 3146 odbc pc regains the internet connection back I am passing Connection string in the query itself still when executed it is nt refreshing the connection inspite of internet being working properly if i close the program and run again then the problem is solved...bt i want to handle this error and reset the connection again at run time... Does anyone know how to Reset this connectionstring using DAO? Thanks in Advance! Last edited by kirti_sm25; Jul 29th, 2009 at 07:43 AM. Reply With Quote Jul 29th, 2009,02:47 PM #2 si_the_geek View Profile View Forum Posts Super Moderator Join Date Jul 2002 Location Bristol, UK Posts 38,317 Re: Error Number : 3146,ODBC--call failed. Thread moved to Database Development forum (the "VB6" forum is only meant for questions which don't fit in more specific forums) If the problem is with the ODBC connection, I don't think there is anything you can do - because you are not in control of it at all. If the problem is somehow with CompTemp, you may be able to get past the error by closing and re-opening it. (July 2007 to June 2017) . . . . . . . . . . Hitchhiker's Guide to Getting Help at VBForums Classic VB FAQs (updated Oct 2010) ...Database Development FAQs/Tutorials (updated May 2011) (includes fixing common VB errors) .......... (includes fixing common DB
question and get tips & solutions from a community of 418,605 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"