Reporting in Your Applications with Embarcadero RAD Studio

List & Label is a reporting component that integrates with applications to provide them with rich reporting capabilities. It allows developers to create sophisticated reports based on data from any source. Easy data binding for your own VCL applications is provided by List & Label’s FireDAC component, which supports numerous data sources such as Oracle, MS SQL Server, SQLite, DB2, MySQL and PostgreSQL, as well as many other databases and formats. The control over the data for reporting always remains with the application itself.

Service Pack 26.001 for List & Label and the Report Server

The first Service Pack for List & Label 26 has been released. What are the new features and improvements? In this blog post we give you an overview. Each entry was taken directly from the English Readme.

Autosize for Column Widths

Another step forward in our continuing quest to improve what's already great – our table object. Until LL25, you had to decide which widths you'd like to reserve for your respective columns. While this works out just nice most of the time, sometimes the result is less than perfect.

Supporting SVG as Image Format

The Scalable Vector Graphics format has been around for quite a while. The first specification was released in 2001, and meanwhile all browsers offer solid support for SVG. During the years, we've received a couple of requests to support SVG in List & Label. Initially, I was hoping for Microsoft to make SVG rendering support a Windows feature that we could just use. However, that hasn't happened so far. And so we had to come up with a different solution.

Using Your Own .NET Designer Objects in Unmanaged Code – Designer Object Bridge

Many things can often be implemented significantly easier and faster in managed code than in unmanaged code, such as with Delphi or C++. Sometimes, there already exist ready-made .NET modules which contain the desired requirements and which need to be used in your own unmanaged application. But the question then is: How can a .NET module be made accessible to an unmanaged system?

Building a Better Databinding Ecosystem for Delphi

Data provider for Delphi

The IDataProvider interface for .NET has enabled many features that are not available for all of the other platforms so far. Most importantly, it brings multiple report containers and nested tables. For C++, we've included a sample in LL21. This is sadly missing in Delphi. In addition, the current Delphi data-binding engine still works against the BDE, a technology that has been deprecated quite a while ago by Embarcadero.