Run-Time Error 1004 on Certain Machines

**yay_excel** · 01-13-2015, 06:28 PM

We have a macro-enabled template which has been working fine on all machines in the office for ages. Recently, on certain machines only, it has produced "Run-time error 1004: Unable to get the Object property of the OLEObject class."

It works on one machine with Windows 7 Professional installed running the Home & Business 2013 version of Excel. It does not work on another Windows 7 Pro machine running the Professional Plus 2013 version of Excel.

The code which seems to be producing the error:

Please Login or Register  to view this content.

I have tried referencing the OLEObjects by their index numbers instead of as a collection. This produces another error (not the same error as before). I have tried activating each OLEObject prior to retrieving its properties; another error code. I have tried adjusting the security settings in many different ways with no luck.

Does anyone have any idea what went wrong?

(Just in case, here is the ITEM_COMBOBOXES class)

Please Login or Register  to view this content.

**LJMetzger** · 01-16-2015, 04:25 PM

Your problem may be caused by a Microsoft December 14th update.

See http://support.microsoft.com/kb/3025036/EN-US
http://blogs.technet.com/b/the_micro...-updates-.aspx

Additional things that may help:
From one of the links above: The problem may be corrected by deleting temporary files like *.exd and EXCEL.box in %AppData%\Roaming\Microsoft\Forms and in %temp%\VBE.

a. Make a copy of the offending sheet
b. Delete the original offending Sheet
c. Rename the copy back to the name of the original

I hope this helps.

Lewis

**yay_excel** · 01-17-2015, 01:32 PM

Thank you for your reply!

I was able to sort this out on Tuesday by deleting the .exd files as suggested. I also followed Microsoft's instruction for disabling new security features in 2013 through the registry.

"This issue occurs because some scriptable controls are made obsolete in Office 2013 for security reasons. This is by design, and these errors are expected. These scriptable controls are disabled by using a version-specific kill-bit that only applies to these controls, and this only happens when they are used in a document. We recommend that you do not try to embed scriptable controls directly into documents, because this behavior may reduce system security." http://support.microsoft.com/kb/2793374

I'm not sure if both actions were necessary but they solved the problem. Thanks again.