NADABAS Technical Documentation

Technical and contributor documentation for NADABAS.
Author

Statistics Norway

NADABAS is the National Accounts Database System used to compile national accounts statistics with Microsoft Excel, VBA, and SQL Server.

This documentation is maintained with the source code. Changes are reviewed in GitHub pull requests and are expected to describe the versioned behaviour of the repository.

NoteDocumentation foundation

The architecture section provides a source-verified baseline and evidence register. The VBA internals section migrates the retained technical draft into reviewable, source-linked pages. Environment-specific behaviour still requires testing in supported NADABAS installations.

Start here

  • Getting started introduces the source layout and local validation workflow.
  • Export VBA explains how to create a complete text-based export from an Excel add-in.
  • Import VBA explains how to build a review add-in from the version-controlled source.
  • VBA security scanning explains the scanner, severity model, and narrow approval process.
  • Contributing defines the complete contribution and pull request workflow.

Explore the system

  • Architecture describes the current system boundary, components, data flows, and trust boundaries.
  • VBA internals explains startup, Excel events, workbooks, database access, domain workflows, administration, and localization.
  • International review and localization defines a traceable review protocol for multi-country and multilingual use.
  • Database defines the database documentation scope.
  • Excel integration defines the boundary between Excel, VBA, and external services.
  • Reference will provide exact, source-verified component and interface details.
  • Operations will cover administration, diagnostics, backup, restore, and release activities.

Documentation roadmap

The current increment adds source-linked VBA internals and a coverage register for the retained technical draft. Later increments will add runtime evidence, supported-platform details, operations, and release documentation.

Incomplete material should be tracked as a GitHub issue rather than left as an unowned placeholder in published documentation.