What happened when you added the dubug.print/msgboxes?

norrislaketn wrote:

I have tried several methods.
1) Assigning it to a ctrl key such as ctrl a - skips the called macro
2) Assigning it to a menu button - skips the called macro
3) Running it from the tools, macro, macros menu tree and manually running
the macro. It works in this senero only.

The issue is the end users do not have the patience to use methiods 1 or 2.

"Dave Peterson" wrote:

I thought the problem was when the user hit the shortcut key:

When using a call function in a macro to excute a different macro and using
the shortcut key, it skips the called macro.

Did you try putting the breakpoint in? How about the debug.print/msgboxes?

norrislaketn wrote:

All macros are in the same module and workbook. there are no duplicate macro
names. I have the macro being started by a menu button so the user does not
have to use any shift or control keys

"Dave Peterson" wrote:

Does the second macro open another workbook?

Does your shortcut key combination include the shift key?

If yes, to both, then try changing the shortcut key combination to something
else--don't include the shift key.

norrislaketn wrote:

When using a call function in a macro to excute a different macro and using
the shortcut key, it skips the called macro. But when the macro is selected
in the tool macro menu selection and manually run it works. Is there a
method to slow down the orginal macro until the called macro is completed?

Thanks in advance...

--

Dave Peterson


--

Dave Peterson


--

Dave Peterson