We have built several windows (both .NET and Delphi) solutions using FlexCel and we have experienced the good evolution of the product. We like it mainly for the three following reasons: Value for the money: There is no need for any other component to have a full reporting solution. Performance: From the real experience we have performed, FlexCel is very well engineered and the performance you can obtain with it is impressive! The source code is available, and it's very important if you are involved in the development of competitive solutions and products.
- Luis del Ser
Another vote for Flexcel here, since the rewritten and updated Flexcel came out a year or two ago, I only use that. Mostly I use it to read XLS and XLSX files, which it does much faster and more flexibly than Excel automation, in my experience. If you also need to write XLS and XLSX files (which I do occasionally) Flexcel has the most amazing utility named 'ApiMate'. You can design your output report in Excel, including only a minimum of actual data, but with all the detailed formatting, headings, and column, row and cell properties you need. Then point ApiMate at the Excel file, and it generates a Delphi program to write the entire XLS file using the Flexcel API, with all the attributes matching those you created in Excel itself. It is then the work of a few moments to adapt the ApiMate-created functions to handle your real data. Magic! Flexcel support is prompt and helpful, too.
- Tim Frost
I think I've been spoiled by TMS. IMO TMS blows away everyone in terms of components offered for Delphi...
- Jeremy Fisher via TMS newsgroup
I was very impressed with the speed of your grid as some of the files being loaded are > 30000 rows, the performance is still very good. Although I don't use many of the newer advanced features I have found it to be a very solid work horse.
