In order to use mdblib as a dynamically loaded library,
there must be a set of functions for accessing the
application-level data in the MDB data structures.
Instances of the structures can then be retained and
passed to the lib as opaque pointers. The application
doesn't have to know anything about the data types
I have taken a first cut at supplying missing functions
for accessing some frequently used fields.
The attached diff file is based on CVS source on