J
John Keith
I have several excel applications that build their own command bar interfaces.
I use application.IgnoreRemoteRequests = true to force any new instances of
excel to open seperate from the one with specialized command bars.
This works well until I try to open (2x click an xls file) a new
excel-instance that also modifies the commandbars. I am attempting to
create a button on the Worksheet Menu Bar that will execute the locally
(module with-in the active instance) available "MyMacro". Any one of these
works exactly like I expect when run stand-alone. But when I launch one that
is the 2nd or higher instance of excel, the open process stops after loading
the base-excel-shell (my default command bars appear, but no workbook is
opened). I can then click "open" and again select the xls file, which opens
the workbook as expected, creating the new command bar button properly.
Any thoughts on what is going on?
I use application.IgnoreRemoteRequests = true to force any new instances of
excel to open seperate from the one with specialized command bars.
This works well until I try to open (2x click an xls file) a new
excel-instance that also modifies the commandbars. I am attempting to
create a button on the Worksheet Menu Bar that will execute the locally
(module with-in the active instance) available "MyMacro". Any one of these
works exactly like I expect when run stand-alone. But when I launch one that
is the 2nd or higher instance of excel, the open process stops after loading
the base-excel-shell (my default command bars appear, but no workbook is
opened). I can then click "open" and again select the xls file, which opens
the workbook as expected, creating the new command bar button properly.
Any thoughts on what is going on?