Henry Ing-Simmons

Thanks for your prompt and thorough response. I have tried doing it like this: ```csharp var footerTable = wordDocument.Footer.Default.AddTable(1, 3, WordTableStyle.TableNormal); footerTable.WidthType = TableWidthUnitValues.Pct; footerTable.Width = WordTableGenerator.OneHundredPercentWidth; var footer =...

Yh with the standard `.AddPageNumber` method I didn't get that popup.

Do you know what's needed to achieve that - is it just a lot of refactoring? I would offer to help but I likely won't have much time - though...

Anyone monitoring this repo?

@lukejagodzinski give me some credit. of course I've got a tslint.json

@lukejagodzinski my configuration didn't change and then this suddenly started happening so I was hoping it was bug that one of the maintainer might be able to give some advice...

I've been reading through the various issues on this and it seems like a complicated problem. So I appreciate a proper fix might be a way off. However, are there...

> confirm that the orderings are the culprit by comparing the raw SQL performance with and without the orderings in simple SQL test @roji This is exactly what I did....

@roji ok great. Is the EF version tied to the .NET version? We've only just upgraded to .NET 6 so we won't be moving to 9 any time soon. @stevendarby...

Running `exec sp_updatestats` on our database has actually resolved the querying performance for us