Duplicate declaration in current scope

**Turbobiker** · 10-30-2009, 05:30 AM

In a macro i created i want a macro to preform similar actions on more than
one sheet. I put it all in one macro (string is the same, just the worksheetname different, but it now gives me the error:

"Duplicate declaration in current scope"

What can i do about it?

**royUK** · 10-30-2009, 05:33 AM

The macro needs changing, post the code - remember to use Code Tags

**Richard Buttrey** · 10-30-2009, 05:34 AM

Hi,

Instead of declaring the variable with a Dim statement in every procedure, define the variable as a Public variable i.e. Public stSheetName as String, and put this outside any procedures as the top of a Module.

HTH

**Turbobiker** · 10-30-2009, 05:52 AM

Hold on: Here it goes:

(when it gives the comment, the debug mode automatically selects the rule:
"Dim Found0 as range")

Please Login or Register  to view this content.

**Turbobiker** · 10-30-2009, 05:53 AM

Please Login or Register  to view this content.

Sorry, it's to long to post in one post

**royUK** · 10-30-2009, 06:18 AM

To best describe or illustrate your problem you would be better off attaching a dummy workbook, the workbook should contain the same structure and some dummy data of the same type as the type you have in your real workbook - so, if a cell contains numbers & letters in this format abc-123 then that should be reflected in the dummy workbook.

If needed supply a before and after sheet in the workbook so the person helping you can see what you are trying to achieve.

Doing this will ensure you get the result you need!

**Turbobiker** · 10-30-2009, 10:01 AM

talked it over with my supervisor and he would like each product to have theyr own Macro.

But because we have about 15 products i don't want to make 15 buttons.
Is there a way to make them follow up automaticly? (without pressing the button again)??

**romperstomper** · 10-30-2009, 10:10 AM

Yes - just have another macro that calls them all - for example:

Please Login or Register  to view this content.

replacing Macro1 with the name of your first macro, and so on.
Note: if all of your macros basically do the same thing but with slight variations, your code can probably be made a lot more efficient, but we would need to see it.

**royUK** · 10-31-2009, 04:31 AM

If the actions are similar, then I would think that one macro could easily be enough. It's just a case of declaring variables usually. Howvwer, without an example workbook that's the best you will get