In a spreadsheet, I created several buttons that simply jump to a different tab when clicked. Here is the macro code:
Sub Jump1()
'
' Jump1 Macro
Sheets("Pt View Option1").Select
End Sub
It works fine for me, but when I sent it to my son and he runs it in his Excel (we both have version 2007), he gets runtime error 32809 (application or object defined error). Any ideas why it would not work for him? He does have macros enabled in his Trust Center Settings.
-Does the sheet exist?
-Is the sheet hidden?
It's hard to replicate,send a sample the offending workbook
No sheets are hidden. The jumps to another tab work find for me, but when I sent a copy to my son, he gets the runtime error. Another problem I have is an ActiveX spin control works for me, but when my son clicks on it, it doesn't work. How can I send you the spreadsheet?
Hi
Are the buttons Activex controls and has your son updated Windows with the early December 2014 update. There was a bug in the update which affected workbooks that used Activex controls.
Here's the text of an email I sent to all my clients whose workbooks I support.
Hello Bill,
Mmmm. We have our friends at Microsoft to thank for this. See discussion here and the many scathing comments.
[URL="http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/13/forms-controls-stop-working-after-december-2014-updates-.aspx"]
I suspect that you too have installed the early December 2014 updates from MS.
I had deliberately held off updating my system with the December updates having learnt from experience in the past. I prefer to wait and see if I hear of any problems. As I mentioned my system was working fine when I tested your files. I had planned last night to install the updates which I did overnight. Imagine my horror when I checked this morning and found my system was now exhibiting the same problem you encounter. Not only that but the system restore point I had carefully created (again from long experience) would not restore when I tried to restore my system to the pre December updates.
I googled around and found the link I mention above, among many others in a similar vein.
This site mentions a subsequent MS fix, KB 3025036. When I googled this I found the following Microsoft support item
http://support.microsoft.com/kb/3025036
On this page you'll see a 'Fixit' button that you can click to fix it automatically, (or it can apparently be done manually by deleting all .exd files which is a bit of a faff and not something I looked forward to doing). When I clicked the Fixit button it downloads a small program which you can run and after it finishes (it only takes a few seconds) it seems to have fixed the problem. I'm still holding my breath and am totally cheesed off with Microsoft for subjecting everyone to this problem, many of whom will not have an IT support service to easily fix it.
Try this and let me know. You'll obviously need to apply this on every PC on which you've updated the December updates.
Regards
Richard Buttrey
RIP - d. 06/10/2022
If any of the responses have helped then please consider rating them by clicking the small star iconbelow the post.
Dear Richard Buttrey - You saved my life. Thanks a lot!!
Hi Richard
I have been searching everywhere on the internet for a solution to this issue. Thanks very much for posting this solution.
The macro name makes me believe it is not an activex control
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
,
Bookmarks