Microsoft Access Run Time Error 3146 Odbc Call Failed
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 13:45:03 GMT by s_wx1196 (squid/3.5.20)
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
Ms Access Error 3146
viewing messages, select the forum that you want to visit from the selection below. odbc call failed access 2013 Results 1 to 5 of 5 Thread: Error (3146) ODBC --call failed Tweet Thread Tools Show Printable Version Subscribe to this Thread… 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 http://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_other/access-2007-odbc-call-failed-error-3146-only-on/27172fb8-958f-4222-be8e-9083541c8891 Unanswered: 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 http://www.dbforums.com/showthread.php?1664131-Error-(3146)-ODBC-call-failed both. This isn't a 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, Visu
2002. The following code segment executes the first read, from rs, successfully, but gives me a "Run-time error 3146 ODBC--call failed" on the second one from rs1. Both rs and rs1 are queries. Can anyone give me information on this error? Dim db as Database Dim rs http://www.pcreview.co.uk/threads/run-time-error-3146-odbc-call-failed.1865044/ as Recordset Dim rs1 as Recordset Dim strUserID as String Dim strProgram as String Set db = CurrentDb Set rs = db.OpenRecordset("SELECT program_id FROM sysuser WHERE sysuser_id = '" & strUserID & "'", dbOpenDynaset) rs.MoveFirst strProgram = rs!program_id If Right(strStartLoc, 2) = "10" Then Set rs1 = db.OpenRecordset("SELECT * FROM report_db WHERE enabled = '" & strUserID & "'", dbOpenDynaset) .... End If -- Carol Guest, Jun 9, 2005 #1 Advertisements Guest Guest Try and run the queries, see if you get this error message. error 3146 Running the query, not by code, will give you the odbc call failed, and then it will give another message, of what is the real error. If the query will run, then run the code, put a break before the open recordset, copy the string of the SQL to the immidiate window ?"SELECT program_id FROM sysuser WHERE sysuser_id = '" & strUserID & "'" and copy it to a new query and run, it will give you the real error. And as a side note 1. try odbc call failed and run the tables, mybe you are not connected to the server 2. Is user id is text type, if not then the sql should look like "SELECT program_id FROM sysuser WHERE sysuser_id = " & strUserID "Carol Grismore" wrote: > I am using Access 2002. The following code segment executes the first read, > from rs, successfully, but gives me a "Run-time error 3146 ODBC--call > failed" on the second one from rs1. Both rs and rs1 are queries. Can anyone > give me information on this error? > > Dim db as Database > Dim rs as Recordset > Dim rs1 as Recordset > Dim strUserID as String > Dim strProgram as String > > Set db = CurrentDb > Set rs = db.OpenRecordset("SELECT program_id FROM sysuser WHERE sysuser_id = > '" & strUserID & "'", dbOpenDynaset) > > rs.MoveFirst > strProgram = rs!program_id > > If Right(strStartLoc, 2) = "10" Then > Set rs1 = db.OpenRecordset("SELECT * FROM report_db WHERE enabled = '" & > strUserID & "'", dbOpenDynaset) > .... > End If > > -- > Carol Guest, Jun 9, 2005 #2 Advertisements Guest Guest These are some good ideas, but I have actually done all this and no errors occur. Any further ideas would be appreciated. -- Carol "Ofer" wrote: > Try and run the queries, see if you get this error message. > Running the query, not by code, will give you the odbc call failed, and then > it will give another message, of what is the real