You need to reorganize your code. A module can call a class module but a
class module cannot call a moulde. You need to exit the class module.

Probably your solution is to split your class module up into a differnt
number of functions. Then from the module routine

1) Call Class function 1 ( Init function)
2) Call Class function 2

"rick" wrote:

I have a workbook that has about 50 sheets and makes extensive use of vba.
However, I now have created an IribbonUI interface and am getting a Catch-22
in the various calls.
In ThisWorkbook class module I have set the iribbonui to a property. The
ribbon_onLoad is in another module and loads fine. However, if I try to call
another subroutine (Workflow, which is the routine that activates sheets an
invalidates ribbon controls) the controls will not invalidate until
the -onLoad routine exits.
Here is where I am stuck. Is there some way that I can get another event to
fire which I can then use to call the workflow module?

Summary:
Used to be: Workbook_Open called -- Workflow (Error 91 Object variable not
set - because Ribbon_onLoad would not run until Workbook exited).
Is now: workbook_Open exit sub - RibbonUI-onLoad fires but I can't call
Workflow from it.

Need a workaround to be able to trigger another event or do a goto outside
of the Subroutine.

Thanks for your assistance.

.... rick

.