Page 1 of 1
IMPLEMENTED - Exporting data in MS Excel format
Posted: Mon May 04, 2009 2:46 pm
by Daniel Mentlik
Microsoft Excel is one of the most widely used systems for calculation of simple results using spreadsheets. Clarity can now export its own data in ASCII format, which can be then imported into MS Excel. Being able to export the data from Clarity in the excel format from the start would simplify the process.
Do you want DataApex to include this feature? Vote in the poll and discuss the feature in this thread to fasten the process!
Internal issue tracking ID: 9939
Re: Exporting data in MS Excel format
Posted: Wed Jun 17, 2009 8:58 am
by IFL
Hello,
if you are planing to implement Excel-export what is about OpenOffice Calc export files? Is this the same format?
Thank you.
Claus
Re: Exporting data in MS Excel format
Posted: Wed Jun 17, 2009 9:28 am
by Petr Kohutek
Open Office Calc can usually open the MS Excel format. I have experienced problems only with complicated excel files containing macros.
Thank you for suggestion we will take Open Office Calc into consideration.
Re: Exporting data in MS Excel format
Posted: Wed Jun 17, 2009 10:53 am
by Petr Kohutek
Together with the development of the Excel supporting features in Clarity we plan to prepare several examples of macros solving common tasks. You can use them freely and modify it to suit to your requirements. If you can, please share your improvements with others by posting the improvements back to the Clarity forum or to DataApex.
Please send us any
- suggestions for solutions that you would like to do with Excel, we will try to address the most popular ones
- Description of your Excel solutions - Examples of your excel sheets would be very helpful
- Comments to our macros - let us know if it works, eventual problems, etc.
This feedback will help us to better design the planned Excel supporting features in Clarity.
First of the macros is available here:
Excel - export Clarity result table, compare with limits
Re: Exporting data in MS Excel format
Posted: Fri Jan 21, 2011 3:29 pm
by Daniel Mentlik
The issue was implemented in Clarity 3.0.2.244