In production since 2008  ·  VB6 + ASP.NET

A whole business system, with far less code.

A metadata-driven RAD framework: you lay out the screen with low-code controls and the engine generates all the CRUD — SELECT, INSERT, UPDATE, DELETE, navigation and auditing. A complete data-entry screen takes ~7 lines.

~7
lines per screen
2
platforms, 1 model
6
chart types via SQL
frmCadCargo.frm VB6
' Full CRUD screen — the engine reads DataField/TypeControl
' of each control and generates the CRUD automatically.
Private Sub cmdBotoes_Click(Index As Integer)
  Select Case Index
    Case CMD_SALVAR:   FormSalvar Me, "tbcargo", ucCodigo, "codcargo"
    Case CMD_EXCLUIR:  FormExcluir "tbcargo", "codcargo", ucCodigo
    Case CMD_PROXIMO:  FormLerRegistro Me, "tbcargo", ucCodigo, "codcargo", , , ProximoRegistro
    Case CMD_SAIR:     Unload Me
  End Select
End Sub
550k → 75k
Real case · NeXT ERP

NeXT's own ERP migrated from VB6 to ASP.NET with this model and went from ~550,000 to ~75,000 lines of code — about 86% less, the same system.

Extracted from NeXT ERP Access · MySQL · SQL Server Metadata-driven CRUD Desktop → web bridge SQL-driven dashboards
A category of its own

The low-code framework for VB6 — and the bridge to the web.

"There's no low-code framework for VB6," they say. There is: it's NeXT LowCode SDK. Metadata-driven controls generate the CRUD inside VB6 itself — and the same model runs on ASP.NET, opening the path to the web. See how it works →

The problem

Every CRUD rewrites the same data layer.

Every screen repeats SELECT, INSERT, validation, binding, navigation, auditing. Multiply that by dozens of screens and two platforms.

Without the SDK

  • — SQL written by hand on every screen, with injection and inconsistency risk.
  • — Binding and formatting (currency, date, tax IDs) copied field by field.
  • — Auditing and multi-company forgotten on half the screens.
  • — Migrating desktop → web means relearning everything from scratch.

With NeXT LowCode SDK

  • → Declare DataField + TypeControl; the engine generates parameterized SQL.
  • → Formatting, masking and validation built into the controls.
  • → time_stamp, codusuario and codempresa filled in by default.
  • → The same programming model in VB6 and ASP.NET.
How it works

Metadata on the screen. CRUD at runtime.

Three steps — and the same screen runs on desktop or web, without relearning the paradigm.

01

Lay out the screen

Drag the low-code controls (ucText, ucCombo, ucGrid…) and point each one to its column with DataField and its type with TypeControl.

02

Call the engine

One line — FormSalvar / FormLerRegistro — and the framework walks the controls, builds the SQL and persists with auditing.

03

Run it anywhere

The same screen design and the same calls exist in the VB6 SDK and the ASP.NET SDK — the natural path from legacy to the web.

VB6 Desktop  ·  modForms.bas
' Save and navigate
FormSalvar Me, "tbcargo", ucCodigo, "codcargo"
FormLerRegistro Me, "tbcargo", _
    ucCodigo, "codcargo", , , ProximoRegistro
C# ASP.NET  ·  FormHelper.cs
// Same model, on the web
FormHelper.FormSalvar(form1, "tbcargo", txtCodigo, "codcargo");
FormHelper.FormLerRegistro(form1, "tbcargo",
    txtCodigo, "codcargo", operacao: ProximoRegistro);

One API, two runtimes. If you know VB6, you already know the web version.

Features

A mature runtime layer — not a throwaway generator.

Every feature was validated in real production, not in a demo.

Metadata-driven CRUD

SELECT / INSERT / UPDATE / DELETE generated from DataField + TypeControl, always parameterized.

Low-code grid + property page

Configure columns (field, title, width, type, editor) through a visual property page — or by code.

New

SQL-driven dashboards & charts

Pie, bars, area, treemap, gauge and KPI — each fed by a single SQL query. One line per chart.

VB6 → ASP.NET bridge

The same paradigm on both platforms: modernize legacy at your business's pace.

Configurable multi-database

Access (Jet), MySQL and SQL Server from the same codebase — the dialect is adapted at runtime.

Auditing & multi-company

time_stamp, user and company applied by default on every write. No more forgotten WHERE.

Masks & validation

Tax IDs, phone, postal code lookup, currency and date — validation and formatting built into the controls.

Standard toolbar & navigation

New, Save, Delete, Next, Previous, Find — one handler, form states ready to go.

Inline records & lookup

Combos with a detail button open the entity's own screen; code lookup with search and copy.

Sales dashboard with SQL-driven charts
The differentiator

A BI dashboard you write in SQL.

The chart and KPI controls take a query and draw themselves — in the label, value pattern. Change the SQL, change the chart. No external library, no third-party service.

' Sales by salesperson — bars
ucChartBar1.CarregarSQL _
  "SELECT f.nome AS rotulo, SUM(v.valortotal) AS valor " & _
  "FROM tbvenda v JOIN tbfuncionario f ON v.codfun=f.codfun " & _
  "WHERE v.data BETWEEN #ini# AND #fim# GROUP BY f.nome"
Two platforms

One programming model. Wherever your system lives.

SDK VB6

Maintain and extend legacy

UserControls (.ctl) + connection and form modules. For teams that keep desktop systems running and need speed without a rewrite.

  • ▸ 16 ready-made low-code controls
  • ▸ Data-entry engine (modForms)
  • ▸ Native GDI+ charts, no dependencies
  • ▸ Navigable demo included
SDK ASP.NET

Take it to the web without starting over

DatabaseHelper + FormHelper + UserControls (.ascx) on Web Forms. The same screen design, now in the browser.

  • ▸ Parameterized DAL (anti-injection)
  • ▸ 13 IFormControl UserControls
  • ▸ Masks, address & city lookup
  • ▸ Direct VB6 migration path
See it running

Two sample apps, ready to explore.

Built entirely with the SDK — the same code you would write.

Library demo screen

Library

A complete catalog and loans app — the "hello world" of metadata-driven CRUD.

// full screen in ~7 lines
Commercial Management demo screen

Commercial Management

Customers, products, quotes and the sales dashboard with SQL-driven charts. In VB6 and .NET.

// same model, desktop and web
Pricing

Per-developer license. Royalty-free runtime.

The license covers design-time. What you ship to your clients runs with no per-install fee.

Indie
Solo developer
US$ 349 / dev · perpetual
Binary (OCX/DLL) · optional ~20% annual maintenance
  • ✓ Full VB6 SDK
  • ✓ Low-code controls + form engine
  • ✓ Demos (Library + Commercial Management)
  • ✓ Documentation and templates
  • ✓ 1 year of updates
Subscribe
Most popular
Pro
Small team / integrator
US$ 899 / dev · perpetual
Binary (OCX/DLL) · optional ~20% annual maintenance
  • ✓ Everything in Indie
  • ✓ ASP.NET SDK (bridge to the web)
  • ✓ Dashboard / chart controls
  • ✓ Extra screen templates
  • ✓ Email support
Subscribe
Enterprise
ISV / multiple devs
US$ 2,290 · perpetual
Source code included · multi-dev license · ~20% annual maintenance
  • ✓ Everything in Pro
  • ✓ Multi-developer license
  • ✓ Source code access
  • ✓ Priority support
  • ✓ Annual maintenance
Talk to sales
Per-developer (seat) license, valid at design-time — the runtime is redistributable and royalty-free. Perpetual + annual maintenance (~20%) model, node-lock activation, 30-day trial and self-service reactivations.
Frequently asked

What developers ask.

Is there a low-code framework for VB6? +

Yes — it's NeXT LowCode SDK. Contrary to what you often read, you can indeed have a metadata-driven low-code framework inside VB6 itself: controls that generate the CRUD automatically, without leaving the environment. And the same model runs on ASP.NET, opening the path to the web. In production since 2008.

Is it a code generator? +

No. The SDK generates no code for you to keep and maintain. The controls carry metadata (DataField, TypeControl) and the engine reads that metadata at runtime to run the CRUD — so there is no scaffolded code to fall out of sync with your database.

Do I need to rewrite my system to use the SDK? +

No. The SDK is incremental: you adopt the controls and the engine screen by screen, alongside your existing code. New screens are born low-code; the old ones keep working.

Which databases does it work with? +

Access (Jet 4.0), MySQL and SQL Server from the same codebase. You write in one dialect and the runtime adapts the query to the provider configured at the installation.

What's the difference between the VB6 and ASP.NET versions? +

The programming model is the same — DataField, TypeControl, FormSalvar, FormLerRegistro. What changes is the runtime platform: desktop (VB6) or browser (ASP.NET Web Forms). It's the path to migrate desktop → web without switching paradigms.

Do the charts depend on any external library? +

No. In the VB6 version they're drawn with native GDI+; each control takes a SQL query in the label, value pattern and renders itself. No CDN, no third-party service.

Do I pay royalties for each app I distribute? +

No. The license is per developer (design-time). The runtime is redistributable and royalty-free — you ship as many installations as you want to your clients.

Get in touch

Watch a screen come to life in ~7 lines.

Request a guided demo, ask questions — or subscribe now by picking a plan.

Request a demo

I reply personally. No spam.

Prefer to talk directly?

Ready to subscribe? Pick a plan above and click Subscribe — you'll go to the store.