-
I should add that the most obvious solution to this problem is to import the data into a worksheet, and then create a pivot table based on that data.
This will not work for my situation because we need to be able to handle 65,000+ rows, so the data must be stored in the pivot itself.
Our users cannot use Excel 2007 to avoid the 65k row limit.
Regardless. I should be able to set up a pivot table based on a SQL Server table/view which only has 350 rows without waiting a century for it to complete, especially when I've proven it can complete in under 30 seconds in every other situation.
Last edited by PegLegPete; 03-16-2009 at 11:47 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules