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
We have been using TMS components in our software development for almost 30 years. Throughout this time, we have consistently experienced friendly and high-quality service. Problems are not simply dismissed with the words "no error found," but rather, solutions are actively sought in collaboration with the customer. The components are well-designed and highly configurable to meet individual needs. We have also found TMS to be a reliable partner in custom development projects.
- Holger Hanschmann
I appreciate all the time and effort you guys put into maintaining and enhancing this great suite of components. Though I only really start again using Delphi after some years "off track" with a new project I am working on, using them really saves me lots of time as I can have a sexy looking interface with great usability without needing to "draw" this myself from standard components. Big win!
- Matthias Böge via TMS Forum
Every time I call on TMS I find the same level of professional attention and timely response. Thank you very much! I'm a TMS fan for life
- Tony Benci via email
I work with Delphi since the first version, and searching for components is a hard work (I think you know). I've tested tons of components, even the "best-sellers", in my eyes, there are two things importants to look for a component: the "look" (for visual components of course), and the most important:
It need to be easy to understand, to programming, and to find information when it is needed (help/manual/demos)
In all of these points your job is really good! Congratulations for you and your team.