Attachments are only available to registered users.
I have done that but the problem remains.
Design Mode, Control Properties, View Code and Run Dialog are all active but Insert (spanner, hammer, etc) is greyed out and inactive.
I am pretty sure I set it to ALL when I first tried to add a new button in Excel 2010 a week or two ago.
I did that but the Insert button is still inactive.
If it means anything, in the XML section, which I have never used and have no immediate plans to, also has a number of inactive buttons - Map Properties, Refresh Data, Import and Export. Souce and Expansion Packs are active.
And in Modify the Document Panel is inactive.
These are not a problem but perhaps there is some common issue.
It seems to be a problem with existing Excel 2010 Files that I have worked on with VBA. They would have started as 2003 or 2007 and been migrated but not had any buttons added.
I have a plain (no VBA) Excel 2010 file that does have active Insert.
I have customised (with VBA) Excel 2007 files that have active Insert.
There does seem to be some relationship with version and previous VBA work.
New 2010 workbooks have the Insert button
Old 2003 and 2007 work books not migrated to 2010 also have it.
But some saved as Macro-Enabled in 2010 seem to lose it.
Having said that I just tried saving an old 2007 in 2010 as Macro-Enabled and it has Insert active working.
But not the one I have been working on.
Hi JessThe wiki send repeatedly has an error while loading.
Is there anything special about file that I should consider?
Something I noticed is that there is a ! in Excel symbol.
Problem solved. While trying to upload the dummy file I started wondering what the exclamation mark meant and I realised it meant file was protected. Which I knew but to me the protection was for data fields not the sheet as a whole. Dumb I know because I selected the unprotected fields and then protected everything else. And that protected the workbook against Inserts. I removed protection and I can now insert my new button.
So all good. Thanks for help. Just going through a systematic trouble shooting process with an objective guide did the trick.