HYPTUSS 11.71 ControlCommandButton1

[johnstevens77]

I just downloaded this version but when I try the command buttons, I get the message that the 'ControlCommandButton1' cannot be created. I am using Windows 7 and Active content is enabled.

john

[Breelander]

I just downloaded this version but when I try the command buttons, I get the message that the 'ControlCommandButton1' cannot be created. I am using Windows 7 and Active content is enabled.

What is perhaps more relevant than the version of Windows is what version of Office you are using. Also, is it any button, or particular button(s) on a particular sheet? It will help the developers if you can be more specific.

[kiloran]

I just downloaded this version but when I try the command buttons, I get the message that the 'ControlCommandButton1' cannot be created. I am using Windows 7 and Active content is enabled.

john

Have you made any changes to your downloaded version before you saw the error? If so, what happens if you download a fresh copy and try it without any changes?
Which command button are you using?
What version of Excel (2003, 2010, 2016, etc)? Is it 32-bit or 64-bit (note: not your Windows 7. Even if Windows 7 is 64-bit, it is recommended to use 32-bit Excel)

--kiloran

[Itsallaguess]

I just downloaded this version but when I try the command buttons, I get the message that the 'ControlCommandButton1' cannot be created. I am using Windows 7 and Active content is enabled.

Have you made any changes to your downloaded version before you saw the error?

If so, what happens if you download a fresh copy and try it without any changes?

I think the answers to these two key questions will be the most interesting for me too, so thanks kiloran.

Cheers,

Itsallaguess

[johnstevens77]

Thanks for the replies. I am using Excel 2007. When I create my portfolio onto the vanilla version it updates the prices and forecast yields OK, I then 'save as' and close the file. Next time I open it, none of the buttons work.
I made a test just now using a new download version, enabling active content and then adding 100 Aviva along with BP. The prices and yields uploaded OK and I saved the file as 'test' and closed it. Upon reopening, none of the buttons work.

john

[ReformedCharacter]

Thanks for the replies. I am using Excel 2007. When I create my portfolio onto the vanilla version it updates the prices and forecast yields OK, I then 'save as' and close the file. Next time I open it, none of the buttons work.
I made a test just now using a new download version, enabling active content and then adding 100 Aviva along with BP. The prices and yields uploaded OK and I saved the file as 'test' and closed it. Upon reopening, none of the buttons work.

john

Try downloading another copy, and instead of 'save as', just 'save'. Do you get the same problem?

RC

[Breelander]

Have you made any changes to your downloaded version before you saw the error? ...

I think the answers to these two key questions will be the most interesting for me too...

I am using Excel 2007. When I create my portfolio onto the vanilla version it updates the prices and forecast yields OK, I then 'save as' and close the file. Next time I open it, none of the buttons work.

I have a machine with Windows 7 and Office 2007. I'll see if I can reproduce the problem...

[Breelander]

I have a machine with Windows 7 and Office 2007. I'll see if I can reproduce the problem...

Yes, I can.

'Save As > Excel Workbook' strips out the VB code. It does warn you that it will be a 'macro-free' workbook and that 'VB Project' won't be included.

In order to preserve the Macros you need to use either 'Save As > Excel Macro-Enabled Workbook (*.xlsm)'or 'Save As > Excel 97-2003 Workbook (*.xls)'.

No, Excel 97-2003 works after the first save only, subsequent saves seem to kill the macros without warning you. Use *.xlsm, that can be saved repeatedly and will continue to work.

[AJC5001]

I have a machine with Windows 7 and Office 2007. I'll see if I can reproduce the problem...

Yes, I can.

'Save As > Excel Workbook' strips out the VB code. It does warn you that it will be a 'macro-free' workbook and that 'VB Project' won't be included.

In order to preserve the Macros you need to use either 'Save As > Excel Macro-Enabled Workbook (*.xlsm)'or 'Save As > Excel 97-2003 Workbook (*.xls)'.

No, Excel 97-2003 works after the first save only, subsequent saves seem to kill the macros without warning you. Use *.xlsm, that can be saved repeatedly and will continue to work.

How strange Is this something that has changed recently?

I have Excel 97-2003 Workbook (*.xls) format for all my HYPTUSS for years - currently with Windows 10 and Office 365 Excel Version 1909 which as far as I am aware are up-to-date.

Adrian

[johnstevens77]

I have a machine with Windows 7 and Office 2007. I'll see if I can reproduce the problem...

Yes, I can.

'Save As > Excel Workbook' strips out the VB code. It does warn you that it will be a 'macro-free' workbook and that 'VB Project' won't be included.

In order to preserve the Macros you need to use either 'Save As > Excel Macro-Enabled Workbook (*.xlsm)'or 'Save As > Excel 97-2003 Workbook (*.xls)'.

No, Excel 97-2003 works after the first save only, subsequent saves seem to kill the macros without warning you. Use *.xlsm, that can be saved repeatedly and will continue to work.

I think that that will work, I saved the previous version as macro enabled. Will give it a go now

john

[johnstevens77]

Well, that seems to be fine at the moment. I ran a test adding Acacia Mining and Aviva,(not that I hold Acacia Mining!). Acacia mining caused a run-time error-2147012879 (80072ef1). As soon as I deleted Acacia Mining, it worked as it should. Now to recreate my HYP.

Thanks

john

[johnstevens77]

Macro enabled works fine.

john

[Breelander]

How strange Is this something that has changed recently?
I have Excel 97-2003 Workbook (*.xls) format for all my HYPTUSS for years - currently with Windows 10 and Office 365 Excel Version 1909 which as far as I am aware are up-to-date.

This behaviour (removing macros when saving as *.xls) seems to be specific to Excel 2007. By default 'Save' seems to use its standard *.xls format which doesn't include macros. You have to save as *.xlsm to reliably preserve macros. Saving as ' Excel 97-2003.. (*.xls)' does include macros, but opening then saving it again seems to 'update' it to the 2007 *.xls format (minus the macros).

Macro enabled works fine.

Glad to hear that

[Itsallaguess]

This behaviour (removing macros when saving as *.xls) seems to be specific to Excel 2007. By default 'Save' seems to use its standard *.xls format which doesn't include macros.

You have to save as *.xlsm to reliably preserve macros. Saving as ' Excel 97-2003.. (*.xls)' does include macros, but opening then saving it again seems to 'update' it to the 2007 *.xls format (minus the macros).

Thanks for your valuable help with this issue Bree, it's great when we can get some extra eyes on these types of issues.

Cheers,

Itsallaguess

[Breelander]

Thanks for your valuable help with this issue Bree, it's great when we can get some extra eyes on these types of issues.

I'm happy I was in a position to help, it's good to be able to give something back in return for all the work you and Kiloran do on this.

[peterh]

How strange Is this something that has changed recently?
I have Excel 97-2003 Workbook (*.xls) format for all my HYPTUSS for years - currently with Windows 10 and Office 365 Excel Version 1909 which as far as I am aware are up-to-date.

This behaviour (removing macros when saving as *.xls) seems to be specific to Excel 2007. By default 'Save' seems to use its standard *.xls format which doesn't include macros.
You have to save as *.xlsm to reliably preserve macros. Saving as ' Excel 97-2003.. (*.xls)' does include macros, but opening then saving it again seems to 'update' it to the 2007 *.xls format (minus the macros).

Glad to hear that

The xlsm format was introduced when Microsoft revamped the Excel file structures with Excel 2007. Any file containing VBA modules in Excel 2007 or later has to be saved as an xlsm file.