https://communities.sas.com/t5/ODS-and-Base-Reporting/Finding-the-problem-in-ExcelXP/m-p/70187#M8056 Hi, Jack:<BR /> I hate that error message in Excel. When I get it it's usually because I've tried to do something funky with the XML (like passing an XML string into Excel using PRETEXT or POSTTEXT -- really not happy with that one) or doing something with styles or formulas that Excel didn't like. I used to get it all the time when I had a title statement in the code -- before the tagset allowed embedded titles.<BR /> <BR /> I don't have a good way to tell what exactly caused the error in a particular instance, but I do know that when I work with ExcelXP, I keep making numbered copies of my programs. When I get the error, I fall back to the last known program that Excel opened successfully and then ask myself what changed between the working program and the program that Excel gave the error with.<BR /> <BR /> I tried looking down in that error file that Excel logs, but generally don't find it useful.<BR /> <BR /> cynthia<BR /> <BR /> ps...sometimes, the updated tagset for ExcelXP fixes things. Mon, 19 Jan 2009 23:05:56 GMT Cynthia_sas 2009-01-19T23:05:56Z https://communities.sas.com/t5/ODS-and-Base-Reporting/Finding-the-problem-in-ExcelXP/m-p/70186#M8055 I am creating a workbook with the ExcelXP tagset, version (SAS 9.1.3, v1.70, 06/05/07). <BR /> <BR /> When I try to open it, I get the messages:<BR /> <BR /> =====<BR /> Problem During Load<BR /> <BR /> Problems came up in the following areas during load:<BR /> <BR /> Strict Parse Error<BR /> <BR /> This file cannot be opened because of errors. Errors are listed in C:\Documents and Settings\c449630\Local Settings\Temporary Internet Files\Content.MSO\8F5FDA51.log.<BR /> =====<BR /> <BR /> That file contains the following text:<BR /> <BR /> =====<BR /> XML PARSE ERROR: Malformed or illegal processing instruction<BR /> Error occurs at or below this element stack:<BR /> (Stack is empty--error occurs at or below top-level element.)<BR /> =====<BR /> <BR /> I don't find that helpful. How do I determine what the problem is and where it occurs? Mon, 19 Jan 2009 21:12:04 GMT https://communities.sas.com/t5/ODS-and-Base-Reporting/Finding-the-problem-in-ExcelXP/m-p/70186#M8055 JackHamilton 2009-01-19T21:12:04Z https://communities.sas.com/t5/ODS-and-Base-Reporting/Finding-the-problem-in-ExcelXP/m-p/70187#M8056 Hi, Jack:<BR /> I hate that error message in Excel. When I get it it's usually because I've tried to do something funky with the XML (like passing an XML string into Excel using PRETEXT or POSTTEXT -- really not happy with that one) or doing something with styles or formulas that Excel didn't like. I used to get it all the time when I had a title statement in the code -- before the tagset allowed embedded titles.<BR /> <BR /> I don't have a good way to tell what exactly caused the error in a particular instance, but I do know that when I work with ExcelXP, I keep making numbered copies of my programs. When I get the error, I fall back to the last known program that Excel opened successfully and then ask myself what changed between the working program and the program that Excel gave the error with.<BR /> <BR /> I tried looking down in that error file that Excel logs, but generally don't find it useful.<BR /> <BR /> cynthia<BR /> <BR /> ps...sometimes, the updated tagset for ExcelXP fixes things. Mon, 19 Jan 2009 23:05:56 GMT https://communities.sas.com/t5/ODS-and-Base-Reporting/Finding-the-problem-in-ExcelXP/m-p/70187#M8056 Cynthia_sas 2009-01-19T23:05:56Z