Print Spooler Depedency

[Jay]

OS: Windows 10 .19042 x64

Excel: Excel 365.14026 x64

FXL: 191029 Dyn Array

Was running into some issues with spreadsheets processing time that throwing more powerful hardware at wasn't helping much.  After getting the trial (which I will be buying) I did some refactoring, this particular one is not as painful.

I use both Mac and Windows and in Windows Excel I run into an issue where the process doesn't respond and gets hung up on the "Print Driver Host for Applications" and/or splwow64.exe which requires the process to be manually terminated to move the calculation forward (whether using FXL or not).  After various troubleshooting with MS, deleting printers, new drivers, etc. it seems like disabling the print spooler on this machine solved that problem.  However, when running the profiler with Print Spooler disabled then throws a VBA run-time error 1004, "Unable to set the Orientation property of the PageSetup class".  Enabling the print spooler again then fixes FXL.

The obvious answer is of course to figure out how to permanently solve the print spooler issue but since it seems to be a recurring issue over time with MS, it would be nice if possible to forego whatever check in the FXL code that depends upon the print spooler as an option.

If someone has a great answer for the underling issue, I would love to hear it.  Not sure if the print spooler issue is the source of inconsistent profiling issues on certain worksheets where single thread performance is quicker than full recalc which seems like should never be the case.  If the process is hung by the spooler then I could certainly understand why that happens but is there something else I'm missing from a performance perspective?  Nothing in the formulas makes me think this would be the case nor am I using any VBA code.

Thanks and appreciate the fine work Charles.  I could have used this for many years now to solve a lot of problems.

[Charles Williams]

Jay, Thanks for reporting this.

I did a quick test but cannot duplicate the problem:

looking at the code FXL is supposed to ignore errors with pagesetup.

Which profiling command are you using?

Is any FXL output produced?

What does the Status Bar show?

I assume you do not have Break on all errors checked in the VBE?