error "The macros in this project are disabled"

[Guest]

I can create small VBA/Excel macros and functions and run them just fine.
But when I insert a large function ("xxx"), put "=xxx()" into a cell,
and click F9, VBA complains that "The macros in this project are disabled."

This never used to happen; But I recently had my IBM thinkpad T23 replaced
and my files restored onto the new HD.

The help message suggests that this is because the .wks was opened "with
macros disabled", and suggests that I close it, then reopen it "with macros
enabled".

How do I do that? And is that really the problem?

How do I get around this problem?

I'm running Excel 2000 on Windows 2000, version 5.0, service pack 4.

Thanks in advance for your help!

 

[Tom Ogilvy]

If security is set to high, macros are disabled without prompt.

 

[Dave Peterson]

Tools|macro|macro security|security level tab

But after you change it, you have to close and reopen the workbook.

 

[Guest]

There are some caveats to all of this... With security set to high, you will
get prompted to run macros if the code has been digitally signed. If it is
not digitally signed, then macros will automatically be disabled with
security set to high. If it is digitally signed, opened, and the digital
signer's code is accepted, then every time that a program is open that is
digitally signed by that individual, it will automatically open without
prompting and run the macros.

With security set to medium, you will be prompted each and every time if you
wish to run the macros or not.

With security set to low, there will be no prompt and all macro code will run.

Now, here's the big caveat. Something that I have run across. If you have
Office 2000 installed, include Visio 2000. If you install Visio 2003 without
uninstalling Visio 2000, then macros will not run in Excel 2000 with security
settings at medium or high. I do not know if this is because of the way it
was installed or the package that was installed, but it is something that I
have run across. I have not seen a case where Visio 2003 was initially
installed after Visio 2000 was removed. So I don't know if there was some
sort of conflict in the 2000 vs. 2003 installation, if 2003 visio is not
compatible with office 2000 or if the way that this particular package of
visio 2003 was installed was at fault. People are still investigating.

The words provided by the others here should get you into a functional
working mode at least on your computer. If you go to a different computer
you may end up having to duplicate your efforts.