Microsoft Visual Basic Run-time Error 3146
Contents |
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. run-time error 3146 odbc call failed sql server To start viewing messages, select the forum that you want to visit from run time error 3146 odbc call failed access 2010 the selection below. Results 1 to 4 of 4 Thread: RUNTIME ERROR '3146'..ODBC-Call Failed Tweet Thread Tools Show Printable Version Subscribe run time error 3146 odbc call failed oracle to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 9th, 2005,11:41 PM #1 nagasrikanth View Profile View Forum Posts Thread Starter Hyperactive Member Join Date Nov 2004 access vba runtime error 3146 Location India,Hyderabad. Posts 420 RUNTIME ERROR '3146'..ODBC-Call Failed Hi.. Im using SQL server as my backend and MS Access as F.E.. Im using to update around 10 to 20 records one by one by upto 2 to 3 records it was updating, later for 4th record it was saying "RUNTIME ERROR '3146'..ODBC-Call Failed"(at "rst.update" it was showing) ..at that time if i start agian from "rst.addnew" then
Run Time Error 3146 Odbc Call Failed Mysql
for upto 3 to 4 it was okay..Is there any limitation in adding records.??? FYI: Im not getting if i update 1 or 2 records..and one more thing that i came to know was ,If the table was a ordinary Access Table..Im not getting any error.. One more thing was If i place some time delay using msgbox (like msgbox "Updated..." for example)that means for each record I placed a message updated..then it was working perfectly on to my surprise.. Please help me in this regard..Please.. Thanks & regards Anu... Reply With Quote May 9th, 2005,11:46 PM #2 RobDog888 View Profile View Forum Posts Visit Homepage Super Moderator Join Date Apr 2001 Location LA, Calif. Raiders #1 AKA:Gangsta Yoda™ Posts 60,221 Re: RUNTIME ERROR '3146'..ODBC-Call Failed Sounds like your updating/adding records through Access tables/queries and not directly to the SQL tables? Alos, probably using a recordset to add/update when you could execute a sql INSERT statement or an sql UPDATE statement. Recordsets are slow. You can create a connection to SQL using ADO, DAO, ODBC to perform your actions. VB/Office Guru™ (AKA: Gangsta Yoda™ ®) I dont answer coding questions via PM. Please post a thread in the appropriate forum
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
Odbc Call Failed Access 2013
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 http://www.vbforums.com/showthread.php?338252-RUNTIME-ERROR-3146-ODBC-Call-Failed 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 https://www.experts-exchange.com/questions/27831438/MS-Access-VB-Runtime-error-3146-ODBC-Call-Failed-connecting-to-mySQL.html 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) <
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, http://www.dbforums.com/showthread.php?1664131-Error-(3146)-ODBC-call-failed select the forum that you want to visit from the selection below. Results 1 to 5 of 5 Thread: Error (3146) ODBC --call failed Tweet Thread Tools Show Printable Version Subscribe to this Thread… https://bytes.com/topic/access/answers/206736-odbc-call-error-3146-a Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 02-08-11,15:10 #1 Stium View Profile View Forum Posts Registered User Join Date Jan 2011 Posts 19 Unanswered: Error (3146) error 3146 ODBC --call failed I'm got a situation where I run a set of reports for different areas. Most of the areas work but some I get this error. Error (3146) ODBC --call failed. [Oracle][OCBC][Ora]ORA-00600: internal error code, arguments.In this case I'm having access call an Oracle database. Suggestions that I found would include refreshing the link or dropping the table and adding it again. I've tried both. This isn't a time error 3146 single machine issue, it is happening network wide. Any suggestions? Reply With Quote 02-10-11,12:34 #2 pkstormy View Profile View Forum Posts Moderator Join Date Dec 2004 Location Madison, WI Posts 3,926 I might try re-creating the ODBC DSN. Also make sure that you don't have an ODBC DSN connecting to the same db by another ODBC DSN name. You want all users/computers that are connecting to the db to have the EXACT same ODBC DSN name. A mispelled (or spelled slightly different) ODBC DSN for one user/computer can cause problems for others. (but this usually causes problems for some users and not others). If that isn't the problem, I might try running any dbcc checkdb type commands on the Oracle server against the db (I'm not sure what the Oracle commands are to check the db.) This seems more likely since you said it's for all users. Lastly, when you link the tables, make sure the "Save Password" check box is checked when linking (although this wouldn't cause the problems you noted.) If all else fails, you could also try creating a File DSN versus a System DSN. Expert Database Programming MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0) Reply With Quote 02-10-11,15:21 #3
question and get tips & solutions from a community of 418,590 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 re