These programs show how to use certain aspects of OOFILE and act as a standard
against which each release is validated and results checked on different
platforms.
SUMMARY
ooftest-1.cpp
shows how to declare a single table database, create it and perform operations
to add data, do simple searches and combine selections.
Also makes use of separate files, rather than a single database container.
ooftest-2.cpp
Introduction to relations, shows how to declare a relation between two tables
and add related data.
ooftest-3.cpp
Tests the multi-user mode. Note that on a Mac, the test database needs to be on a shared volume to enable multi-user locking. Personal filesharing on a Mac does
not provide locking for local access to a shared file - you can't run the test program on the machine containing the shared volume.
ooftest-4.cpp, ooftest4.sav
Shows two forms of report output. Keep the ooftest4.sav to compare against
the ooftest4.out you will produce.
ooftest-5.cpp
Lets you test the dbDate field type input, looping around entering sample dates and showing the resulting date parsed from your entry.
ooftest-6.cpp
Shows how to modify related values, testing both direct calls and view-related calls (which would be used by an embedded table editing groups of related records).
ooftest-7.cpp
Shows comparative and range searches on variety of keys
ooftest-8.cpp
Tests the error reporting dialogs.
ooftest-9.cpp
Shows deletion of a single record, with related child records and all records.
ooftest10.cpp
Shows use of streams to create records, eg: for importing data.
ooftest11.cpp
Shows using the test data generator to generate random data to populate a database (taken from a real project).
ooftest12.cpp
Shows declaring compound fields mixing char and binary data, and searching and sorting by their indices.
SPECIAL INSTRUCTIONS
ooftest-3
You must copy the ooftest2.db file produced by ooftest2 and call it ooftest3.db The file will be randomly modified during the multi-user test.
ooftest-6
You must copy the ooftest2.db file produced by ooftest2 and call it ooftest6.db The file will be slightly modified during the test.