This is the database engine.

Look in the file INSTALL on how to install it.
Look in the file APIREF on how to use it.
http://www.fortunecity.se/kista/pcprom/137/gxsnmpdbdoc1.tar.gz
currently contains documentation of the db-api.

First rewrite of the database utilized table-plugins.

In second rewrite those where replaced by a configuration
file describing each table.

This is third rewrite of the database code, and the configuration
file has been moved into the database, in table
"dbfieldconfig". Purpose of this is that the application
can modify dbfieldconfig table, and signal a reread of 
configuration. So the application can run-time modify
the layout of tables. This is usefull if one wants to
for example support user defined data.

BUILD & RUN
try build as normal.
but important dirs is these, in this order:

database3
lib
widgets
app/widgets
app
tools/traps/lib
tools/traps/netmon
plugins/your-database

that should cover all code used in the test.
RUN:

start of configuring gxdb.conf for the 'gxdd' daemon.
then run him: database3/server/gxdd

then start gxsnmp

then go into tools/traps/netmon
and start him too.

netmon should load interface table and
start pinging.

TERMS USED IN THE SOURCE
  TABLE
    Database side:
      this is row(s) serialized and stored in
      a database.
    User side:
      this is row(s) serialized and stored in
      memory.

  ROW, RECORD
    Database side:
      This is field(s) serialized and stored
      in a table.
    User side:
      This is field(s) serialized and stored
      in memory. For example in C language this
      would be stored as a struct.

  COLUMN, FIELD, MEMBER
    Database side:
      this is a single data holder. It has
      different types.
    User side:
      This is a single data holder. In C
      Language it can be of following 
      types:
      - Integer
      - Double
      - Pointer to a char string.