Most reports display some data. Typically, this data is obtained from databases. Therefore, the report has a connection to the data source in order to have a list of available tables and fields, as well as the data itself. But what if at the time of writing the report, you only had a local database that you created a connection to inside the report. Then the report will not work properly. We need a valid connection. There are two ways out of this situation: use a data source from a user program, or replace the connection line in the report.

We connect to MongoDB from a FastReport .NET report through the assembly of the plugin-connector library to the database.

As a rule, controls are placed on dialog forms, with the help of which values ​​are set for further filtering. Often they are connected to the data source using the DataColumn property.

We connect the plugin, which is a connector to the report designer, in order to use the DB2 database. We collect it from the project. The resulting FastReport.DB2.dll library is a plugin.

To create a data source and a connection string to it, use the connector from FastReport. This includes source codes with various demo projects and additions.

The FastReport.Net designer provides a plug-in connector, which must first be assembled in the project. Before creating a data source in a report, make sure that FireBird is configured correctly.

The Vista database is designed to be embedded in the client application as a file. Vista is used in only one application and is not intended to be shared.

No sDB ist ein prominenter Vertreter der NoSQL-Datenbanken. Es wurde für die Verwendung auf der .Net-Plattform entwickelt und ist Open Source. NosDb hat, wie viele andere nicht relationale Datenbanken, eine hohe Geschwindigkeit und eine gute lineare Skalierbarkeit. In diesem Artikel sehen wir uns an, wie Sie mit einem Plug-In für den Designer eine Verbindung zur No sDb-Datenbank im Bericht herstellen.