New DataProvider for Redis

Redis is an in-memory key-value database, so a typical NoSQL database. Since its initial release in 2009, it has become quite popular and now is, according to db-engines.com by far the most popular key-value database out there. With the new RedisDataProvider you can now use your Redis database within List & Label or Report Server.

Supporting Cross-Datasource Relations

The .NET DataProvider concept allows to bind to almost any data source. Basically, it mimics a relational database management system containing tables, relations, sort orders etc. However, often you'll find yourself needing to combine data from different sources, e.g. a server log file that contains customer logins and a SQL customer database that contains all pertinent information about the customers.

Building a Better Databinding Ecosystem 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.

New OpenEdge Data Provider for List & Label 21

This time we feature a guest post from our partner and developer colleague Thomas Wurl. About two years ago, Thomas developed a free data provider for Progress OpenEdge available for all List & Label customers. While this provider was adopted successfully by many Progress users, it suffered some restrictions. So Thomas decided to restart from scratch and came up with an incredibly fast and powerful new solution. Here's his story. 

New and Overhauled Data Providers

The ObjectDataProvider is one of the key providers we ship with LL. It binds to generic lists just as well as to EntityFramework or other Object Relational Mapper data. It is also the final fallback for all datasources that cannot be handled by one of the other providers. In LL21, the provider got a couple of new features for the .NET 4.0 assembly.

New Web Designer

Until version 21, we used browser specific plug-ins or ActiveX controls in order to display the Designer right in the browser. However, browser vendors are more and more restrictive and begin to ban plugins from their browsers altogether. Thus, it was time for a new technology.