Export Spreadsheet Warning

pinbotpinbot Texas
edited 3:00AM in FastReport .NET


I'm exporting to an XML document so that it will open in Excel. I think I've tried Excel exports before but had problems.

With Excel 2007, a warning box comes up and Excel writes a log file.

I can click on "OK" and the document open ok.

Here is the contents of the log written whenever I open an XML file exported from FR.NET:



XML Spreadsheet Warning in Table
REASON: Value too large
ACTION: Limiting value
FILE: I:\TempInternet\Temporary Internet Files\Content.IE5\A7BEAGF6\Changes[2].xml
GROUP: Table
TAG: Column
ATTRIB: Width
VALUE: 1641.39


Comments

  • edited 3:00AM
    Hello,

    Could you send me the prepared report file (.fpx, save from preview) to tz@fast-report.com?
  • pinbotpinbot Texas
    edited 3:00AM

    Attached.

    If you export from FR with this file, you'll see the warning in Excel.



    This is a report created on-the-fly on an .aspx page and then exported.

    How do you export to excel2007? Is it still xml or is there a different fastreport.export component?

    I see a lot of whitespace at the right side of this report. I'll see if I can "trim" it a little and see if that fixes the problem.



    Bryan
  • pinbotpinbot Texas
    edited 3:00AM

    That's what it was.

    The page width was way too big. I trimmed it down some and that fixed the problem. I guess the blank column that FR was inserting was too big.

    The reason I didn't notice it is because this report is only exported to excel (XML).


    How do we export to excel 2007? Still as XML?

    Thanks,


    Bryan
  • edited 3:00AM
    We have separate export filter for Excel2007 which produces .xlsx file.
  • pinbotpinbot Texas
    edited 3:00AM

    What's the namespace/usage?

    In Visual Studio 2008, when I type "fastreport.export.", the list of exports does not seem to include a specific xlsx export.

  • edited 3:00AM
    Full name is FastReport.Export.OoXML.Excel2007Export
  • pinbotpinbot Texas
    edited 3:00AM

    Thanks.

    I guess I didn't drill down far enough.

    Bryan

Leave a Comment