I have a Parent, Child, Grandchild structure where Parent A loads the Child instantly and Parent B takes 5 minutes to load the Child. I think I've isolated the apparent cause of the problem; however I have no clue on how to proceed to solve the problem.

I have two .xlsm spreadsheets which perform financial modeling (call these "Parent A" and "Parent B"). These are both large and complex spreadsheets with lots of VBA code.
  • Each has one Addin checked: QuoteServer.
  • Each has VBA project reference checked: QuoteServer

I have one QuoteServe.xlam spreadsheet which handles requests from both Parents (not concurrently) for market quotes using a variety of sources (call this the "Child").
  • QuoteServer has one Addin checked: RCH_Stock_Market_Functions.xla
  • QuoteServer has VBA project reference checked: RCH_Stock_Market_Functions.xla

RCH_Stock_Market_Functions.xla is written by a third party and specializes in getting quotes from one source (call this the "Grandchild"). It serves the Child exclusively.
  • This has no Addin or VBA project references

Upon opening each of the Parent workbooks:
  • Parent A status bar shows "Calculating (8 Processor(s) 0%" for around 5 minutes before it is ready to use
  • Parent B status bar shows active loading which is completed within 1-2 seconds

I've expermimented with Parent A to isolate the cause of the slow opening:
  • References>QuoteServer (unchecked) Addins>QuoteServer (checked): 5 min delay
  • References>QuoteServer (unchecked) Addins>QuoteServer (unchecked): open and ready immediately
  • References>QuoteServer (checked) Addins>QuoteServer (unchecked): 5 min delay
  • References>QuoteServer (unchecked) Addins>QuoteServer (unchecked): 5 min delay uponn checking Addin QuoteServer

It appears to be clear that the reference to QuoteServer in Parent A causes delay while reference to QuoteServer in Parent B has no effect.

Task Manager shows no Excel CPU or memory activity taking place during this delay.

Any thoughts on what the problem might be and how to go about solving it?

Thank you.

Earl.