Problem running macros

I have several userforms in an .xla file that is accessed from a common drive. I rewrote them all to reduce the file size. To test the new forms before release, I have set the new file up exactly the way I had done the first one, except for the name of the file. That is the only part that has changed. However, none of my excel files will access any .xla files anywhere on my computer or the common drive now. Everyone else is still able to use the first version with no problems, but now original file I had used gives me the same error message and never had before. I keep getting the error that the macro cannot be found. I have tried a detect and repair with my excel installation disc and that has not helped either. Any suggestions? Thank you in advance!

Good evening ginadesign

...and welcome to the forum!!

Without knowing exactly which version of Excel you are using or what error messages etc you are getting, it's quite difficult, but ...

Try deleting all copies of the .xla add-in on the network drive (and anywhere else you might have set it up as an add-in on your machine), without unticking it from the add-ins box in Excel.
When you next open Excel you should get a message saying the add-in cannot be found - remove from list. Say yes and close Excel. When you next open Excel and look at the add-ins box, there should be no trace of the old add-in. This is where we need to be.

Now reinstate the add-in you want to use, open Excel and try enabling the add-in again.

HTH

DominicB

Sorry! I am using Excel 2003. The Error I get is Run-Time '1004': The macro 'ModelForms.xla!Show_Form' cannot be found. A few days ago I tried your suggestion of deleting add-ins and reinstating them. Everyone else can still access the .xla file with no problems, but I cannot

Hi ginadesign

If you've already tried this, and all other users can run the file, then perhaps your installation is at fault.
You have already run the repair feature, but I've never known that to solve a problem.
Maybe a full reinstall is necessary - it sounds a bit drastic, but the steps to completely remove the add-in I've taken you through have never failed for me before ...

HTH

DominicB