A
Andrew Lockhart
I need to run a bit of code in the Excel envionment before any other code is
run.
We have a large number of separate bits of code developed by different
groups that reply on an environment variable. This environment variable needs
to be set correctly before the code runs.
Almost all our existing code base is xla or xll. We have written a COM Addin
to control this environment variable thinking that all COM Addins were loaded
up before the standard OPEN, OPEN1, OPEN2 registry keys were processed.
What we have discovered is that the Class_Initialise code for some of the
global variables in our XLA's is run first then the Connect on our COM Add-In
and then the Aut
pen code of our XLA.
We are looking for some more detail with regards to Excel's Start up process
so that we can get in first. Or there just a race condition between the
registered COM Addins and the OPEN registry keys?
Any info appreciated.
Kind Regards
Andrew Lockhart
run.
We have a large number of separate bits of code developed by different
groups that reply on an environment variable. This environment variable needs
to be set correctly before the code runs.
Almost all our existing code base is xla or xll. We have written a COM Addin
to control this environment variable thinking that all COM Addins were loaded
up before the standard OPEN, OPEN1, OPEN2 registry keys were processed.
What we have discovered is that the Class_Initialise code for some of the
global variables in our XLA's is run first then the Connect on our COM Add-In
and then the Aut
pen code of our XLA.We are looking for some more detail with regards to Excel's Start up process
so that we can get in first. Or there just a race condition between the
registered COM Addins and the OPEN registry keys?
Any info appreciated.
Kind Regards
Andrew Lockhart