Hi James,
Saving file into the client box is one operation requiring high permission
to use the client IO service. We use the MSXML activex control to save the
XMLData in the client disk as the code shows below:
//--------------
var msxml = new ActiveXObject("Msxml2.DOMDocument.5.0"); // this line
requires Office 2003 installed in Client
msxml.async = false;
msxml.validateOnParse = false;
msxml.resolveExternals = false;
msxml.loadXML( PivotTable1.XMLData );
msxml.save( "c:\test.xml" );
msxml = null;
//--------------
However, this code always will fail due to the Access permission. IO access
will take high risk for client because the script from Internet may perform
harmful write operation in the client to damage key files, change
information etc. So there are two methods we can apply:
1. decrease the security setting at client IE to allow this kind of
operation. However, in real environment, this is often very hard to argue
the client users to do so.
2. develop one signed ActiveX component to perform the save operation which
will be long time to the development and the client will have to download
the CAB from Internet to perform the deployment.
So from my view, I'd suggest you can save the XMLdata as one file in the
server side, this way, there is no need for us to consider the security
limitation of IE at client and you can manage all the file at the server
only. One MSDN article introduce this solution to you.
Build an OLAP Reporting App in ASP.NET Using SQL Server 2000 Analysis
Services and Office XP
http://msdn.microsoft.com/msdnmag/issues/03/10/OLAP/default.aspx
Please feel free to let me know if you have any question.
Best Regards,
Wei-Dong XU (WD)
Microsoft Product Support Services
Get Secure! -
www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.