wxReports lays out banded reports over your SQL database and saves them as a JSON file. wxReportsLib is that same engine as a static C++ library, so the report you designed renders identically inside your own application — no report server, no runtime to install.
Targets Windows, Linux and macOS
Nothing published yet
wxReports links wxReportsLib. The designer is not a second implementation that exports a format for another renderer to interpret — it is the same code, and a drift check runs both against the same fixtures. What stands in the print preview is what your application produces.
Pick a driver and a connection string. One report can hold a different SQL statement and a different connection string for each server type.
Write the SELECT in the report's SQL editor. Columns become fields you can place. Parameters are typed and substituted before execution.
Drop fields onto bands. Each band knows when to repeat, when to break the page and when to stay together.
Preview, print, or export a PDF — vector or raster. Or export the resolved data as JSON or CSV.
Aggregate with sum, count, average, minimum or maximum. Stack normally or to 100%. Bucket dates by day, month, quarter or year. Keep the top N and sort by category or by value. Add a second axis, place or hide the legend, and scope a chart to the whole report or to the group it sits in.
The engine draws every bar as a rectangle straight onto the device context. Nothing is placed as a bitmap.
Group on an expression. Repeat the group header on every page, break the page before or after it, keep a group together, and set how many detail rows have to stay with the header.
Show or hide a band with a visible-when or hide-when condition, evaluated per row. A malformed condition fails safe instead of killing the report.
Variables and conditions run in a Lua sandbox, with the report's own values in scope.
if row.net < 0 then
return "overdue"
end
return ""Named styles, conditional formatting, value types, date formats, decimal and thousands separators.
A field can grow with its content up to a maximum number of lines, and push or extend whatever sits below it.
A report file carries SQL and a connection string per server type. Design against SQLite, run against Oracle, without keeping a second report.
| SQLite | Embedded file | sqlite:reports.db |
|---|---|---|
| SQL Server | via FreeTDS | mssql://host:1433/sales |
| MySQL / MariaDB | via MariaDB Connector/C | mysql://host:3306/sales |
| Oracle | via ODPI-C | oracle://host:1521/ORCL |
| PostgreSQL | via libpq | pgsql://host:5432/sales |
Link the static library, load the definition the designer saved, set the parameters, generate. There is no service to run and no second executable to ship.
wxReport report(wxT("Invoice"));report.Load(wxT("invoice.json"), connectionString);report.SetParameterValue(wxT("invoice_id"), wxT("123"));wxString error;if (!report.ExportPdf(wxT("invoice.pdf"), &error)) wxLogError(error);Set a timeout, a row cap, a data cap in MiB and a batch size. Cancel a running generation. Read progress as it moves through its stages. Large result sets stream instead of buffering.
Data, layout, subreport and chart caches, each with build and hit counters — next to counters for SQL executions, Lua evaluations and rendered bands.
Print, print preview, PDF (vector or raster), report data as JSON, report data as CSV.
A preflight pass that lists the problems it found and jumps to the one you select.
The resolved result set, before any layout is applied.
wxReportsData v1 — resolved rows and columns, deliberately without SQL, file paths, connection strings or layout. Safe to keep as a test artefact.
A suite covering every section and element type, all chart types, page formats and margins, parameters, formulas, summaries, subreports, streaming, caches, PDF and JSON export, cancellation, timeouts and resource limits.
Direct download, no account. A row appears here for every package that is meant to exist; it goes live the moment the file is uploaded, with its real size read from disk.
No package has been uploaded yet. The table fills itself in as soon as the first build lands in the downloads folder.
| Platform | Format | File | Size | Get |
|---|---|---|---|---|
| Windows x86 | ZIP | wxReports-dev-windows-x86.zip Portable build. Unpack and run. Built with Visual Studio, static CRT, wxWidgets linked statically. | Size not available | Not uploaded |
| Linux amd64 | DEB | wxreports_dev_amd64.deb System package for Debian and Ubuntu. Planned; the Linux build is a target, not a finished package. | Size not available | Not uploaded |
| macOS x86_64 | DMG | wxReports-dev-macos-x86_64.dmg Disk image for Intel Macs. Planned; the macOS build is a target, not a finished package. | Size not available | Not uploaded |
| Platform | Format | File | Size | Get |
|---|---|---|---|---|
| Source C++ | ZIP | wxReportsLib-dev-src.zip The engine as C++ sources to link into your application. Same code the designer runs on, with its database drivers. | Size not available | Not uploaded |
Both projects are built on wxWidgets and target all three systems. The build documented today is the Visual Studio one; Linux and macOS are the goal, not a finished download.
wxReports and wxReportsLib are in active development. What is settled is on this page; what is not is listed below rather than filled with a guess.