Replies

Why convert?

We haven’t found any issues with the new formats. If you are using an old workbook, leave it as it is. If you use a feature that wont save in the old format, Excel asks you if you want to convert to the new format. You don’t need to convert everything at once.

The default is to save as xlsx. If you have macros, you are warned that these will be deleted unless you save as xlsx. No big deal really.

What you will find is that the xlsx and xlsm files are half the size of the binary formats. Less disk space and open and save much more quickly.

It appears that the problem of not compiling was nothing to do with the undeclared variables.

Somehow, my add-in managed to get a reference to the Ref Edit Control which I don’t use.
When the Ref Edit Control is not found, the module wont compile and simply says there is a compile error in a hidden module even though there is nothing wrong with the code (apart from undeclared variables).
I removed the reference and now all appears to be OK.

Thanks

Thanks. This is even better than I thought was possible.
I can actually change the setting in my macro.

My addin loads Ok, but Trust Center settings cause security prompts when my addin loads additional workbooks. With this object I can now turn off the Trust Centre settings so that the additional workbooks load without prompts.

Thanks for your help.

Sorry, I wasn’t very clear.

I am referring to the Trust Centre settings.

When Trust Centre doesn’t allow a macro to run without user intervention (becuase the settings do not allow macros to run without a prompt), it would be nice to throw up a message, after the user has accepted the macro, to tell the user how to change their Trust Centre settings to prevent the prompt in future.

Any ideas?

You may be interested to look at the Object Navigator in Navigator Utilities which finds all the objects in a workbook, lists them in a listbox, provides details such as whether they are visible or not, where they arem how big they are and a display of what they look like, all on a userform. NU is a free download at http://www.robbo.com.au

Thanks for your help. That is exactly what I wanted to know.
regards

Thanks Hans,

I don’t care if the form is modal in Excel 97. I just want it to work without producing an error message.

If you set a form to be modeless, it still seems to work OK, as a modal form, in Excel 97, but you have to put up with an error message first. I would like the code to work in 97 but without the error message. Is this possible?

Very hidden is great for the average user as long as he doesn’t have a utility such as Navigator Utilities which routinely shows all sheets, including very hidden sheets, and allows you to easily make sheets very hidden and easily unhide them without writing code.

Well it looks like Google Desktop IS THE PROBLEM.
What a shame because I like the Google Desktop. But whatever it is that it does, it’s too much hassle to keep it.
Thanks everyone for taking the time to respond.

regards
Mark

Well it looks like Google Desktop IS THE PROBLEM.
What a shame because I like the Google Desktop. But whatever it is that it does, it’s too much hassle to keep it.
Thanks everyone for taking the time to respond.

regards
Mark

Yes I do have Google Desktop installed. Is that the problem?
I have some add-ins written by others that seem to do the same things as I do but do not casue the problem?
regards
Mark

Yes I do have Google Desktop installed. Is that the problem?
I have some add-ins written by others that seem to do the same things as I do but do not casue the problem?
regards
Mark

I have an addin that calls subroutines in other addins. The main addin calls the subroutines from the other addins after opening the addin and then using the application.run command. This all works fine on Excel 2000, but when I run it on Excel 2003, I get message boxes asking for the addin password when I close Excel. If the addins are not password protected there are no problems. Anyone got any ideas what is going on?

regards
Mark Robinson

I have an addin that calls subroutines in other addins. The main addin calls the subroutines from the other addins after opening the addin and then using the application.run command. This all works fine on Excel 2000, but when I run it on Excel 2003, I get message boxes asking for the addin password when I close Excel. If the addins are not password protected there are no problems. Anyone got any ideas what is going on?

regards
Mark Robinson