K
Khoo, Zi Wei
My web reporting tool is using the Microsoft Office Web Component to generate
graphs in the reporting and graphing page create using ASP. The pivot table
component will take in an XML file (generated during application run time by
parsing dataset result return from an SQL query using SQLOLEDB provider
connected using ADODB) as its data source, and the pivot table will then be
used as the data source for the graphing component to generate a line graph.
My system has few portion of similar application using same technique and
each of them will query from different database or tables with different
query string, but all will use a different result page (which means different
copy of same OWC component will be used) for the graphing and pivot table.
There will normally be no problem during the first run on the application of
a single portion. The problem occurs whenever user switch portion within
application for different type of query. The error will appears to be problem
in loading the XML data into the pivot table, causing the graph can not be
shown. But problem will be resolve by simply refreshing the page for at least
1 time, or if refreshing doesn’t works, clearing the cookies for the browser
will be needed.
This problem doesn’t appear to be happening in the previous version of OWC
XP. It only happens after migration from OWC XP into OWC 2003.
From your point of view, do you think this problem is caused by the OWC
itself, or is something related to the cookies/ cache of the browser.
FYI, i have already try not to cache my asp result page using the <meta
HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">. Do i need to include this meta in
all .asp as well as the xml file generated dynamicly using asp during runtime?
graphs in the reporting and graphing page create using ASP. The pivot table
component will take in an XML file (generated during application run time by
parsing dataset result return from an SQL query using SQLOLEDB provider
connected using ADODB) as its data source, and the pivot table will then be
used as the data source for the graphing component to generate a line graph.
My system has few portion of similar application using same technique and
each of them will query from different database or tables with different
query string, but all will use a different result page (which means different
copy of same OWC component will be used) for the graphing and pivot table.
There will normally be no problem during the first run on the application of
a single portion. The problem occurs whenever user switch portion within
application for different type of query. The error will appears to be problem
in loading the XML data into the pivot table, causing the graph can not be
shown. But problem will be resolve by simply refreshing the page for at least
1 time, or if refreshing doesn’t works, clearing the cookies for the browser
will be needed.
This problem doesn’t appear to be happening in the previous version of OWC
XP. It only happens after migration from OWC XP into OWC 2003.
From your point of view, do you think this problem is caused by the OWC
itself, or is something related to the cookies/ cache of the browser.
FYI, i have already try not to cache my asp result page using the <meta
HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">. Do i need to include this meta in
all .asp as well as the xml file generated dynamicly using asp during runtime?