My VBA project calls its own instance of Excel for "working on stuff".

Is there any method to "fast load" Excel in this case? My laptop can take
5- 7 seconds to boot a new instance of Excel with a template loaded.

Nope every instance is it's own stand alone application with no connection to
any other instances.
--
HTH...

Jim Thomlinson


"Vacation's Over" wrote:

My VBA project calls its own instance of Excel for "working on stuff".

Is there any method to "fast load" Excel in this case? My laptop can take
5- 7 seconds to boot a new instance of Excel with a template loaded.

You can launch excel from the command line with excel /automation and no add
ins will be loaded - this is usually faster than normal. Try that manually,
if it's faster on your PC then you can try this:

Use the wsh object model for access to a command line and then use the
WshScriptExec.ProcessID property to get the PID of the excel instance
created, then use the win32 api to get that process and use it.

But this is prone to error - you have to grab the right instance of excel -
that is an intermediate/advanced thing to try and do.

Good luck.

--
www.alignment-systems.com


"Vacation's Over" wrote:

My VBA project calls its own instance of Excel for "working on stuff".

Is there any method to "fast load" Excel in this case? My laptop can take
5- 7 seconds to boot a new instance of Excel with a template loaded.