G
Guest
H
To provide rich featured excel downloads we are taking advantage of the XML capabilities of Excel 2002
We produce an xml file which has a link to a stylesheet and teh progid instruction to mark it as an Exel file. The stylesheet then transforms the XML document into Workbook XML to display to the client. This way we can minimze data transfer, farm out processing complexity whilst providing full Excel functionality
The problem we have encountered is to do with Macro security.
We have not used any msxml:script in our stylesheet
In Excel XP the Macro Security settings have the folowing impact
High - Stylesheet wont load so you just see the XML as tex
Medium - Stylesheet is used BUT you then get a warning about macros in the spreadshee
Low - loads fin
The situation with Excel 2003 is much better but most clients will be Excel XP
Are there any workarounds for this
This is within a controlled extranet environment so settings can be changed within Excel, but we cannot expect clients to reduce Macro security to low, and preferably they should leave them as high. Given that we are not using Script, I cannot see why the stylesheet is treated as a macro
Any suggestions appreciated
To provide rich featured excel downloads we are taking advantage of the XML capabilities of Excel 2002
We produce an xml file which has a link to a stylesheet and teh progid instruction to mark it as an Exel file. The stylesheet then transforms the XML document into Workbook XML to display to the client. This way we can minimze data transfer, farm out processing complexity whilst providing full Excel functionality
The problem we have encountered is to do with Macro security.
We have not used any msxml:script in our stylesheet
In Excel XP the Macro Security settings have the folowing impact
High - Stylesheet wont load so you just see the XML as tex
Medium - Stylesheet is used BUT you then get a warning about macros in the spreadshee
Low - loads fin
The situation with Excel 2003 is much better but most clients will be Excel XP
Are there any workarounds for this
This is within a controlled extranet environment so settings can be changed within Excel, but we cannot expect clients to reduce Macro security to low, and preferably they should leave them as high. Given that we are not using Script, I cannot see why the stylesheet is treated as a macro
Any suggestions appreciated