You are hereoffice
I have a client that is dependent on Excel 2007 and a bunch of macros written in vba to run their business. Some of the users let me know today that, all of a sudden, the macros that run when the worksheet file is opened are throwing a debug error.
The error is "object doesn't support this property or method" which is a runtime error of 438.
When I tried checking some things in the interactive window after clicking on the debug option, I couldn't get any object values to be available in VBA. For instance, checking the value of a button's visibility gave me the same error the user was getting. It was acting like none of the objects in the worksheet even existed!
After a little trial and error, I figured out that the users having the problem had applied the "Tuesday Night Security Patch" from Microsoft and started trying to narrow things down.
I pulled the Excel specific stuff first (just one file, really) and that didn't do it.
So, I kept digging...
I had a user report that, all of a sudden, anytime they cut or pasted something in Excel 2003 running on Windows 7, Excel would crash.
We'd had a problem before with Skype and Bluetooth causing Excel to crash, but when I checked this setting in the registry, it WAS set to zero as needed:
HKLM\SOFTWARE\Microsoft\Office\Excel\Addins \BtOfficeAddin.BtOfficeIntegration.1\LoadBehavior REG_DWORD 0x0
Change the LoadBehavior key from 3 to 0, if needed. In this case, it was already 0.
So, that left the user still having the problem...
Did this help you? You can help me!
Did you find this information helpful? You can help me back by linking to this page, purchasing from my sponsors, or posting a comment!
+One me on Google:
Follow me on twitter: http://twitter.com/mojocode