![excel vba get activex value from another workbook excel vba get activex value from another workbook](https://www.journalofaccountancy.com/content/dam/jofa/issues/2015/jan/techqa5.jpg)
I've had a long search through your pages to see if this question has been answered before but having browsed through about 50 pages worth of threads I couldn't see anything, but if I am repeating prior information I do apologise. Summa summarum - it could be an idea to check whether the two machines have different version numbers for the MSCOMCT2.OCX files. Regsvr32 c:\windows\system32\MSCOMCT2.OCX (not sure if this was necessary, but I didn't think it could hurt). Regsvr32 /u c:\windows\system32\MSCOMCT2.OCX Then, finally I unregistered the old DLL via I then rebooted the machine - still no luck. I then copied the MSCOMCT2.* files from work, made a backup of them at home and copied those from work to my C-drive (Windows XP - c:\windows\system32\ ). I had a light-bulb moment and wondered whether there was a difference in the version numbers for MSCOMCT2.OCX at work and at home. My problem was that a userform defined with Excel at work (containing DT pickers) gave the message in the title when opening it at home. Thought I'd append my experience of the above problem - you can find all sorts of references to it everywhere. Please can anyone advise? Is there a checklist I can work through? I've read Īny pointers or guidance would be appreciated. I've checked on the Vista Machine's Local Security Policy window but I can't find anything relevant in there.įinally, I've tried several xlsm spreadsheets on the Vista machine and all of them have the same problem, so its not the actual spreadsheet that is the issue. I've seen posts talking about Default Security policy disabling VBA, but we don't use Group Policy much, and certainly not to control Excel. I've tried to replicate the settings I have in Excel on my W7 machine on to the Vista Excel machine, but it makes no difference. In the macro Settings window, I have "Disable all macro with notification" selected and "Trust access to the VBA project object model" selected. But Macro Security is, and when I change macro security, it makes no difference. The Visual Basic and the Macros buttons are not available. So is the digital Certificate for VBA Projects.īut most of the buttons on the Developer Tab are greyed out. I have Googled, and checked that VBA is installed using Office Shared Features. On a Vista machine, when we open the spreadsheet we get the subject error.
![excel vba get activex value from another workbook excel vba get activex value from another workbook](https://www.exceldemy.com/wp-content/uploads/2021/06/copy-cell-to-another-sheet-by-defining-name6-1030x619.jpg)
On my machine, the spreadsheet works fine. Spreadsheet with VBA was written in an older version of Excel (2003, I think).