Access 2007 Error 3847
Search Community Links Social Groups Pictures & Albums Members List Calendar Search Forums Show Threads Show Posts Tag Search Advanced Search Find All Thanked Posts Go to Page... Page 1 of 2 1 2 > Thread Tools Rating: Display Modes 11-26-2008, 05:40 AM #1 kate10123 Registered User Join Date: Jul 2008 Posts: 185 Thanks: 0 Thanked 1 Time in 1 Post Error message 3847 rewrite code from DAO to ADO Hi guys, I am trying to pull data from a database to another database through an oracle view. How can I change the code I am using for the transfer process to work with ADO?. The reason for this is because we have moved from access 2003 to 2007! Quote: Option Compare Database Option Explicit Public Const db_name As String = "TEST" Public Const jup As String = "TEST" Public Const pwd As String = "TEST" Public Const uid As String = "TEST" Public Const dbq As String = "TEST" Public Const dsn_main As String = " Do not remove or your scheduled tasks will cease to function 7" Public Const dsn_alt As String = "(Oracle in ORACLE_HOME)" Dim dsn_use As String Private Function Get_Local_Number(tbl As String) As Long 'Establish number of records in tbl Dim dbs As DAO.Database Dim rst As DAO.Recordset Set dbs = CurrentDb Set rst = dbs.OpenRecordset(tbl, dbOpenTable) Get_Local_Number = rst.RecordCount rst.close dbs.close Set rst = Nothing Set dbs = Nothing Get_Local_Number_Exit: Exit Function Get_Local_Number_Err: Select Case Err.Number Case Else DoCmd.SetWarnings True MsgBox Err.Number & Chr(13) & Chr(10) & Err.Description End Select Resume Get_Local_Number_Exit End Function Private Sub Get_ODBC_Number(tbl As String, _ drv As Integer, _ num As Long, _ con As String) On Error GoTo Get_ODBC_Number_Err 'Establish number of records in Oracle tbl via ODBC. Dim wrkODBC As Workspace Dim conODBC As Connection Dim rstODBC As Recordset dsn_use = dsn_main Set wrkODBC = CreateWorkspace("ODBCWorkspace", _ uid, _ pwd, _ dbUseODBC) Set conODBC = wrkODBC.OpenConnection("Connection1",
28, 2009. Pierre Doré Guest Migrated this MS ACCESS 2002 to 2007 with the .mdb format. Application starts but when I initiate a command button that runs code to connect to ORACLE I get the following error message: ODBCDirect is no longer supported. Rewrite the code to use ADO instead of DAO. [3847] Here is an extract of the code where it fails: Set gWorkspace http://www.access-programmers.co.uk/forums/showthread.php?t=161331 = CreateWorkspace("ODBCWorkspace", "ACIIS_ADMIN", "aciis8adm", dbUseODBC) gWorkspace.DefaultCursorDriver = dbUseODBCCursor Set db_ACIIS_ORACLE = gWorkspace.OpenDatabase("ACIIS", dbDriverComplete, False, "ODBC;UID=" & "ACIIS_ADMIN" & ";PWD=" & "xxxxx" & ";DSN=ACIIS") Call PULL_OLTF_TO_ACIIS_ACCESS LAST_SYNCH__START_TIME = Now() Me.Start_run_txt.Value = LAST_SYNCH__START_TIME Call Truncate_Oracle_ACIIS_TABLES Call PUSH_PERSON_TO_ORC Call PUSH_AC_TO_ORC Call PUSH_MODULE_TO_ORC ... ... Here is a very small extract of the PUSH_MODULE_TO_ORC Subroutine: Private http://www.office-forums.com/threads/error-3847-rewrite-code-to-use-ado-instead-of-dao.683953/ Sub PUSH_MODULE_TO_ORC() On Error GoTo PUSH_MODULE_TO_ORC_ERROR ccontext = "In PUSH_MODULE_TO_ORC" Shell "explorer G:\ACIISDB" ' Activate the link between server WHQ11 and hqclfs Dim tmp_rs As Recordset Dim RecCounter As Double ... ... 'These are the VALUES to be INserted in ORacle sqlins = sqlins & " values(" & _ MDB_MODULE_CD & ", " & _ MDB_mod_of_day & ", " & _ MDB_start_dt & ", " & _ MDB_module_template_cd & ", " & _ MDB_module_lang & ")" db_ACIIS_ORACLE.Execute (sqlins) Pierre Doré, May 28, 2009 #1 Advertisements Stefan Hoffmann Guest hi Pierre, Pierre Doré wrote: > Migrated this MS ACCESS 2002 to 2007 with the .mdb format. Application > starts but when I initiate a command button that runs code to connect to > ORACLE I get the following error message: > > ODBCDirect is no longer supported. Rewrite the code to use ADO instead > of DAO. [3847] This is a pretty straight forward error me
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Microsoft Corporation › Microsoft Access › Error 3847 How To Fix Microsoft Access Error 3847 Error Number: Error 3847 Error Name:ODBCDirect is no longer supported Error Description: ODBCDirect is no http://www.solvusoft.com/en/errors/runtime-errors/microsoft-corporation/microsoft-access/3847-odbcdirect-is-no-longer-supported/ longer supported. Rewrite the code to use ADO instead of DAO. Developer:Microsoft Corporation Software:Microsoft Access Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows 10, http://www.pcreview.co.uk/threads/when-trying-to-create-workspace-get-error-3847.3865367/ 8, 7, Vista, XP and 2000 Symptoms of Error 3847 "Error 3847" appears and crashes the active program window. Your PC frequently crashes with Error 3847 when running the same program. “ODBCDirect is no longer access 2007 supported” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your computer periodically “freezes” for a few seconds at a time. These 3847 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Microsoft Access) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 3847 error occurs access 2007 error is a critical piece of information in troubleshooting the problem. Causes of Error 3847 Corrupt download or incomplete installation of Microsoft Access software. Corruption in Windows registry from a recent Microsoft Access-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Microsoft Access-related program files. Another program maliciously or mistakenly deleted Microsoft Access-related files. Runtime Errors such as “Error 3847” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. Runtime Errors Knowledgebase Article ID: 128368 Article Author: Jay Geater Last Updated: 27-09-2016 Popularity: star rating here Download NowError Fix Learn More Tweet Recommendation: Scan your PC for computer errors. How To Fix Microsoft Access Error 3847 Below is a list of troubleshooting steps to resolve your Error 3847 problems. These troubleshooting steps get progressively more difficult and time consuming, so we strongly recommend attempting them in ascending order to avoid unnecessary time and effort. Please Note: Click the [ ] image to expand the troubleshooting instructions for each step below. You can also click the [ ] image to hide the instructions as you proceed through each step. Step 1: Repair Registry Entries Associated with Error
Guest Original application in MS Access 2002. When migrated to A2007 the following line Set gWorkspace = CreateWorkspace ("ODBCWorkspace", "ACIIS_ADMIN", "aciis18dev", dbUseODBC) Note that this workspace was define in a seperate module: Public gWorkspace As Workspace generates the error message below: :ODBCDirect is no longer supported. Rewrite the code to use ADO instead of DAO. [3847] Here is the code in full for this section: Set gWorkspace = CreateWorkspace("ODBCWorkspace", "ACIIS_ADMIN", "aciis18dev", dbUseODBC) gWorkspace.DefaultCursorDriver = dbUseODBCCursor Set db_ACIIS_ORACLE = gWorkspace.OpenDatabase("ACIIS", dbDriverComplete, False, "ODBC;UID=" & "ACIIS_ADMIN" & ";PWD=" & "aciis8adm" & ";DSN=ACIIS_TEST") Pierre Doré, Aug 5, 2009 #1 Advertisements Pierre Doré Guest Also note that I've added one reference that ADO required,ADO Ext. 2.8 for DDL & Secrurity, as well I deleted one reference for Microsoft Access 12.0 object library as well as DAO 3.6 object library. Any help very much appreciated. Thx Pierre "Pierre Doré" wrote: > Original application in MS Access 2002. When migrated to A2007 the following > line > > Set gWorkspace = CreateWorkspace ("ODBCWorkspace", "ACIIS_ADMIN", > "aciis18dev", dbUseODBC) > Note that this workspace was define in a seperate module: > Public gWorkspace As Workspace > > > generates the error message below: > :ODBCDirect is no longer supported. Rewrite the code to use ADO instead of > DAO. [3847] > > Here is the code in full for this section: > Set gWorkspace = CreateWorkspace("ODBCWorkspace", "ACIIS_ADMIN", > "aciis18dev", dbUseODBC) > > gWorkspace.DefaultCursorDriver = dbUseODBCCursor > > Set db_ACIIS_ORACLE = gWorkspace.OpenDatabase("ACIIS", dbDriverComplete, > False, "ODBC;UID=" & "ACIIS_ADMIN" & ";PWD=" & "aciis8adm" & > ";DSN=ACIIS_TEST") > > > Pierre Doré, Aug 5, 2009 #2 Advertisements Pierre Doré Guest Actually I was not abel to remove Access 12.0 object library,even though I had read that if using ADO u should remove that reference. "Pierre Doré" wrote: > Also note that I've added one reference that ADO required,ADO Ext. 2.8 for > DDL & Secrurity, as well I deleted one reference for Microsoft Access 12.0 > object library as well as DAO 3.6 object library. > > Any help very much appreciated. > Thx > Pierre > > "Pierre Doré" wrote: > > > Or