The UNICOM Intelligence products access case data using the Provider directly, or indirectly using ADO. There are a variety of ways that third party tools can access case data, depending on the capabilities of the tool.

Tools that have built-in OLE DB support can access the case data using the Provider. SQL Server Integration Services is a tool that has built-in OLE DB support. You can use this tool to transfer case data from any readable data source that Integration Services supports (including readable DSCs) to any writable data source that Integration Services supports (including writable DSCs). Integration Services also has fairly extensive support for reading and writing to text files (fixed format and .csv). The Microsoft Excel file format also has built-in OLE DB support. This makes it easy to import data directly into Excel from any type of data for which a readable DSC is available.

You can use tools like Integration Services to export case data from the UNICOM Intelligence Data Model to other formats, such as Excel, .sav, text files, and so on.

It is easy for VBA-enabled tools to access both the metadata (using the MDM) and the case data (using ADO). For an example, see the Excel VBA example macro included with the UNICOM Intelligence Developer Documentation Library.

You can connect to UNICOM Intelligence Data Model data from ODBC-enabled applications using an ODBC to OLE DB adapter.

You can access case data from Java applications using the UNICOM Intelligence JDBC Driver. For more information, see UNICOM Intelligence JDBC Driver.