company logo

Installing ODABA under MS Windows

Three types of installations are provided for windows:

  • Binaries ( odaba-win- n.n.n _ msver _ cpu , )
  • Source code ( odaba- n.n.n .zip )
  • Documentation ( odaba-doc- n.n.n .zip )
  • Additional plugins ( odaba-plugins- n.n.n .zip )
  • ODABA sample and development databases ( )

where n.n.n refers to the current version number (e.g. 12.3.0). msver is the Microsoft developer studio version used for compiling (e.g. VS2017). cpu defines the processor type (X86 for 32 bit and X64 for 64 bit version).

Binary package

Binary packages are available as .zip file. Since ODABA does not require specific registry entries, installing ODABA simply means unpacking the zip file to an installation directory.

Binaries are provided as 32 bit versions ( : MS DevStudio 2010 and : MS DevStudio 2017) and as 64 bit version ( : MS DevStudio 2017), where n.n.n is the current version number.

Binaries have been build with all features. Dependent libraries (curl, zlib, libzip, hunspell, libmicrohttpd) are included.

Source package

The source package should be used, when another compiler version than MS VS 2010 to MS VS 2017 is required. In this case, the source package has to be recompiled with the required compiler version.


Documentation, which is also provided online, is also provided for local installation. In order to run the documentation system locally, one may download from .

In order to install ODABA documentation, the documentation package has to be copied from the file, where n.n.n is the current version number. In order to start the HTML documentation for ODABA or ODABA GUI, one has to start

  • .../HTMLDoc/odaba/index.html or
  • .../HTMLDoc/odabagui/index.html

In order to install ODABA development databases, the database package may be copied from the file, where n.n.n is the current version number.

Beside several sample databases the package contains the ODABA development databases, which contain the complete ODABA and GUI framework code, as well as design and documentation. This provides direct access to ODABA development resources and allow customizing tools for specific requirements.