Share
Report
16One of my users complained today about an Excel-exported QuickQuery showing the same rows 3 times.
On a closer look I checked that the QQ yields 12006 rows, but the exported Excel has exactly 15000 rows. I have QQ Paging turned on, so when the user requests an Excel dump, a pop-up message appears asking if all the pages has to be counted for. The export procedure then correctly advances up to page 3 exporting the records. The problem is that it always generates the records on page 1. Even so, if I advance pages with the browser arrows, the rows doesn't refresh at all. What we are seeing is always the contents of the first page.
I researched a bit and this was a bug described on KB2724313 that was supossed to be fixed on SL 2011 FP1 which I have. My current QQVIE00.EXE version is 8.10.40521 and it should be past the hotfix involved.
Further research shows that the paging engine might have something to do with the UniqueSort view extended property on a SQL Server level. None of my App QQ views has this extended property. Only QQUserAccessRightView in the Sys database has the property on place.
Is this still an open bug? Did I miss a database upgrade?
I may workaround this by tweaking the MaxSQLRows parameter with Paging turned off, but this may not work for every QQ.
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
