What is the Clarion programming language?

The dictionary is the heart of a Clarion application

Every Clarion application starts with a data dictionary that describes tables, columns, keys, relationships, validation rules and display formats in one place. Screens, reports and processes are then generated from that dictionary, so a change to a field definition ripples through the whole application rather than being repeated in dozens of forms.

This is the single biggest reason Clarion systems age well. The business rules live in structured metadata, not scattered through hand-written UI code, so a system written in the 1990s can usually be recompiled, extended and re-skinned rather than rewritten from scratch.

Templates and code generation

Clarion generates source code from templates. A browse-and-form pattern, a report, a batch process or an entire wizard-driven module is produced by applying a template to dictionary entities. Templates are extensible, which is what allows third-party vendors — Noyantis included — to ship reusable functionality that a developer drops into an application in minutes.

The generated code is ordinary Clarion source, so anything the templates do not cover can be written by hand and embedded at defined points in the generated flow.

What Clarion is good at

Clarion is at its strongest where data volume, transactional accuracy and long service life matter more than visual novelty.

• Order processing, stock control and distribution systems
• Accounting, billing and subscription management
• Job management, field service and scheduling
• Compliance, inspection and audit record keeping
• Systems that must run reliably on-premises with local data

Where Clarion fits in a modern stack

Modern Clarion applications rarely live alone. They expose or consume REST and SOAP APIs, sync with cloud accounting platforms, feed web portals and mobile apps, and store documents in cloud storage. The desktop application remains the operational core while browser and mobile front ends handle customers and field staff.

That hybrid model is usually the lowest-risk path forward for an established business: keep the proven engine, add modern surfaces around it.

Frequently asked questions

Is Clarion still supported?

Yes. Clarion is actively developed and current versions target modern Windows, with third-party template and class vendors continuing to ship new releases.

Which databases can Clarion use?

Clarion talks to SQL Server, PostgreSQL, MySQL/MariaDB, Oracle, Firebird and ODBC sources, as well as its own TopSpeed and legacy ISAM file formats. Many long-running systems are migrated from TopSpeed files to SQL without changing the application logic.

Can Clarion applications produce web or mobile front ends?

The usual approach is to keep the Clarion application as the back-office system and add web or mobile interfaces that talk to the same database or to APIs published by the Clarion application.

Is it hard to find Clarion developers?

The pool is smaller than mainstream languages, which is why many companies retain a specialist partner for maintenance, upgrades and enhancement work rather than recruiting in-house.

Related guides