Excel might not be the right tool for the job. When I hear things like "multiple worksheets/workbooks" and many "cross-references", it sounds to me like what you are really trying to develop is a relational database, and Excel is not a very good tool for something like that. Database programs like Access, or bigger database options like SQL, MySQL, or Oracle are better tools to use for those sort of things.I have a related "not responding" problem with a couple of multi-worksheet workbooks. Each worksheet has many formulas, many cross-references to other worksheets, and several calls to macro subs and functions. There are too many of these items for me to easily use <acronym title="visual basic for applications" style="border-width: 0px 0px 1px; border-bottom-style: dotted; border-bottom-color: rgb(0, 0, 0); cursor: help;">VBA</acronym> debugging methods, although I did incorporate quite a few while the workbooks were still in the development phase.
Excel might not be the right tool for the job. When I hear things like "multiple worksheets/workbooks" and many "cross-references", it sounds to me like what you are really trying to develop is a relational database, and Excel is not a very good tool for something like that. Database programs like Access, or bigger database options like SQL, MySQL, or Oracle are better tools to use for those sort of things.
In the most troublesome workbook, I replaced a complicated formula with a VBA sub. That sub should not be volatile - which is what I have not yet tried out!so what changed a few weeks ago