Did this article resolve your question/issue?



Can't open an Excel file after exporting from ABL


TitleCan't open an Excel file after exporting from ABL
URL Namecan-t-open-an-excel-file-after-exporting-from-abl
Article Number000118080
EnvironmentProduct: OpenEdge
Version: 11.7.x
OS: Windows
Other: Telerik Reporting
Question/Problem Description
Running an ABL procedure to export a Telerik Report document to XLS format using the Telerik Reporting API, the file can't be open with Excel.  It seems that some properties or something configured during the exporting is not allowing the document to be opened. XLS document can be open using LibreOffice and  is open properly, but it looks like there are some extra columns. 
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Issue is a Telerik Reporting API that is exporting the document with garbage in the document, which makes Excel to report a problem with the final document.  ABL is just calling the API and running the methods as any other language. 
Contact Telerik group to resolve the issue with the API and how to format properly the Telerik Reporting template. 
Last Modified Date11/20/2020 6:59 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.