Metadata-driven CRUD
SELECT / INSERT / UPDATE / DELETE generated from DataField + TypeControl, always parameterized.
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.
' 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
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.
"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 →
Every screen repeats SELECT, INSERT, validation, binding, navigation, auditing. Multiply that by dozens of screens and two platforms.
Three steps — and the same screen runs on desktop or web, without relearning the paradigm.
Drag the low-code controls (ucText, ucCombo, ucGrid…) and point each one to its column with DataField and its type with TypeControl.
One line — FormSalvar / FormLerRegistro — and the framework walks the controls, builds the SQL and persists with auditing.
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.
' Save and navigate FormSalvar Me, "tbcargo", ucCodigo, "codcargo" FormLerRegistro Me, "tbcargo", _ ucCodigo, "codcargo", , , ProximoRegistro
// 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.
Every feature was validated in real production, not in a demo.
SELECT / INSERT / UPDATE / DELETE generated from DataField + TypeControl, always parameterized.
Configure columns (field, title, width, type, editor) through a visual property page — or by code.
Pie, bars, area, treemap, gauge and KPI — each fed by a single SQL query. One line per chart.
The same paradigm on both platforms: modernize legacy at your business's pace.
Access (Jet), MySQL and SQL Server from the same codebase — the dialect is adapted at runtime.
time_stamp, user and company applied by default on every write. No more forgotten WHERE.
Tax IDs, phone, postal code lookup, currency and date — validation and formatting built into the controls.
New, Save, Delete, Next, Previous, Find — one handler, form states ready to go.
Combos with a detail button open the entity's own screen; code lookup with search and copy.
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"
UserControls (.ctl) + connection and form modules. For teams that keep desktop systems running and need speed without a rewrite.
DatabaseHelper + FormHelper + UserControls (.ascx) on Web Forms. The same screen design, now in the browser.
Built entirely with the SDK — the same code you would write.
A complete catalog and loans app — the "hello world" of metadata-driven CRUD.
Customers, products, quotes and the sales dashboard with SQL-driven charts. In VB6 and .NET.
The license covers design-time. What you ship to your clients runs with no per-install fee.
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.
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.
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.
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.
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.
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.
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.
Request a guided demo, ask questions — or subscribe now by picking a plan.