Simplified Xbase++ Reporting Tool Integration

Years ago I started developing a class to simplify the integration of List & Label into Xbase++ which I used for all my client's apps. The range of functionality grew with every new task. By now it supports real data preview which is handled in a separate thread.

More Flexibility for Chart Layouts

First of all, on behalf of the whole combit team I'd like to wish you a happy belated new year. I hope you enjoyed the holiday season and start into 2017 with refueled energy. While we're busily working on version 23 already, I'd like to continue sharing some hidden gems in List & Label 22.

Reset Page Count for Group Header

While List & Label has a superior concept for printing mail merges, many other (usually band-type) reporting tools people got used to apply a different concept to print invoices and other mail merge typed projects. Usually in List & Label, you'd define the header data as variables and use text objects, images etc. to design your letter head.

Introducing Long Term Support (Enterprise Edition)

We have a release cycle of approximately one year per major version  – actually it's quite accurately so, we have released the past 10 versions late in October. Coincidentially, this happens to be around my birthday, but that's a different story. It's always a nice present anyway.

Introducing Enterprise Level Logging Support

For you as an enterprise application developer, logging is probably one of the essential features of your app. It enables you to trace and see what the user did just before the app went blank, and see if the typical user answer "I haven't done anything" proves right or wrong. To support you in this task, logging was built into List & Label from the very start.

Breakthrough for Web/Distributed Applications

Repo Source Selection

Until version 22, there was a number of restrictions for web based projects. As the Web Designer is a single project file designer, all the glory that comes with multiple project files like project templates, table of contents and index and – most prominently – drilldown support were not available as they couldn't be designed.