– No luck, the error message quoted above persisted. Next, I tried to copy all the files from Office-VFS\System to a new folder and run regsvr32 for the OCX in that folder.
#Excel treeview code
Unfortunately, this failed with the error message “… the call to DllRegisterServer failed with error code 0x8004005.” – Well, this might have happened because there are some dependencies of MSComCtl.ocx that in the Office-VFS\System folder, which I did not copy. I then ran cmd.exe as Administrator and executedĬ:\Windows\System32\regsvr32 /i C:\Windows\System32\MSCOMCTL.OCX So, I copied the MSCOMCTL.OCX file from the Office virtual files system into the C:\Windows\System 32 folder. The logical next step would be to copy the OCX file to the global System32 directory and register it there. – I was expecting this due to the Office 2016 sandbox. Opening the database, I created with Access 2016 earlier, and then opening the form with the TreeView resulted in in the error “There is no object in this control.”. If I try the same in old Access 2013 installation, I still cannot insert the TreeView controls, as it is still missing from the list of ActiveX Controls. Option Compare Database Option Explicit Private WithEvents m_MyTreeView As TreeView Private Property Get MyTreeView () As TreeView If m_MyTreeView Is Nothing Then Set m_MyTreeView = Me.ActiveXCtl0.Object End If Set MyTreeView = m_MyTreeView End Property Private Sub AddNodes_Click () Dim A1 As MSComctlLib.Node Set A1 = (, tvwChild, "A1", "A1" ) Dim i As Long For i = 1 To 9 "A1", tvwChild, "A1-" & i, "A1-" & i Next i A1.Expanded = True End Sub Private Sub m_MyTreeView_NodeClick ( ByVal Node As MSComctlLib.Node ) MsgBox "You clicked node: " & Node.Text End Sub Redistribution to Access 2013, 2010 and early version of Access 2016 The TreeView visually appears “normal”, displays the sample nodes and a small bit of test code I created, works also as expected, including the event handling. The System subdirectory in the above directory now contains our desperately needed MSCOMCTL.OCX file.Īfter starting my newly installed Access 2016 and creating a new form, I’m immediately able to insert a TreeView Control into this form. For a 64bit Office installation, all files that are not immediately a part of Office will not be installed in the usual, global system directories but in the directory C:\Program Files\Microsoft Office\root\vfs (vfs = Virtual File System). We must be aware of the fact that the C2R-Editions of Office are installed into a semi-virtualized environment (sandbox).
#Excel treeview windows
Installing this did not make any difference regarding the MSCOMCTL.OCX file in the Windows system directories mentioned above. At the time of writing, I got the Version 2003 of Access 2016/365. Then I installed the 64bit Edition of Microsoft 365 Click-to-Run (C2R). The 64bit TreeView with Access 365 (and 2019) If I try to insert an ActiveX Control into an Access form there is no Microsoft TreeView Control available in the list of installed ActiveX Controls.
With a default installation of Microsoft Access 2013 64bit there is neither a MSCOMCTL.OCX file in C:\WINDOWS\SysWOW64\ (this is the system directory of the 32bit subsystem!) nor in C:\Windows\System32 (the default 64bit system directory). I’m very certain that the operating system is not relevant in this context and it will not matter whether this is done on Windows 7, 8 or 10.
#Excel treeview windows 8.1
I started my investigation with an installation of Microsoft Access 2013 64bit in Windows 8.1 (64bit).
No 64bit TreeView with Access 2013 (and 2010)
#Excel treeview how to
Add 64-bit support for mscomctl.ocx, allowing users working in 64-bit versions of Office to create, edit, and open macro files containing the Common Controls.Īs there still is ongoing confusion on how to install and use the 64bit Edition of the Microsoft Common Controls, I decided to investigate the issues and write down my findings.
0 kommentar(er)
