This interface provides a mechanism to allow the database to persist proprietary data in a database.

Most of the interface implementation revolves around persisting proprietary objects,
but this is Not required functionality. Data from objects and files may be stored in the
database without supporting the recreation of the object (or opening of the file).

Besides providing proprietary data storage, searchable data attributes and database
node relationships may be stored in the database by this interface.

Note:
This interface does Not provide any implementation so no type of inheritance is needed.

It is the 'handlers' responsibility to implement the ObjectToJournalNode function to
relate an object to its stored node. Without this functionality, relationships between
data can Not be stored.

This interface manages information for a data source / database type in the following forms:

Inputs : Object, File Path, McDBNode, Clipboard, DataObject
Outputs : Object, File Path, McDBNode, Clipboard, DataObject

Provides a McDataHandler for the McImage COM object, its files and soon it's clipboard formats.

Also, Sinks McImages to monitor and log McImage creation in the Journal.
References NTI's McOpLib, McImageLib (sinked), and McStreams.

PROGID McAddInData.McDataJournal
ObjectFlags Creatable