D
Dan
I have an extremely large Excel XP (SP2) workbook with tables and charts
being refreshed programmatically from SQL Server 2000 (via the
PivotTableWizard method). The amount of data being pulled back grows each
day and, in the last few days, the PivotTableWizard call to refresh one of
the pivottables sporadically began raising a "Problems obtaining data" error
(very informative). The query used to refresh the table returns a ton of
data (18 columns and over 65000 rows); note: the fact that it returns over
65000 rows has not caused problems in the past. Anyway, when I reduce the
amount of data being pulled back the query (by reducing the time span over
which data is drawn), the error stops being raised. Thus, the problem does
SEEM to be related to the amount of data being retrieved--but I'd like to
have a better idea what exactly is going on. Does anybody know whether
there's a limit to the size of queries used to refresh pivot tables? Or,
does anyone have any idea what might be the specific cause of this murky
error message?
Thanks...
Dan
being refreshed programmatically from SQL Server 2000 (via the
PivotTableWizard method). The amount of data being pulled back grows each
day and, in the last few days, the PivotTableWizard call to refresh one of
the pivottables sporadically began raising a "Problems obtaining data" error
(very informative). The query used to refresh the table returns a ton of
data (18 columns and over 65000 rows); note: the fact that it returns over
65000 rows has not caused problems in the past. Anyway, when I reduce the
amount of data being pulled back the query (by reducing the time span over
which data is drawn), the error stops being raised. Thus, the problem does
SEEM to be related to the amount of data being retrieved--but I'd like to
have a better idea what exactly is going on. Does anybody know whether
there's a limit to the size of queries used to refresh pivot tables? Or,
does anyone have any idea what might be the specific cause of this murky
error message?
Thanks...
Dan