When you deploy thin clients and component Servers, you need to ship the production version of all the libraries you used to build them.

If you are using OLE DB, you must also ship the following:

• OSTCDB.dll
  
• OSTCErr.dll
  
• OSTCEnum.dll
  

These are self-registering COM components. If you use Installshield, you need to unpack them using the SELFREG flag to CompressGet, or otherwise arrange to have regsvr32 called for them.

If you have a link-compatible version of osmmtype.dll that is a later version than the one shipped with CSF, use that one instead.

For the DataView Reader, you also need to install the following run-time files in the windows system directory if the versions shipped with the Framework are more recent than those that have been installed already:

• OC30.DLL
  
• OLEAUT32.DLL
  
• OLEPRO32.DLL
  
• mfcans32.dll
  
• mfcuia32.dll
  
• msvcrt40.dll
  
• stdole2.tlb
  
• MFC42.dll
  

The thin client API allows programs to perform the following main tasks:

• Setting Routers
  
• Connecting to a Service
  
• Retrieving Operations from the Server
  
• Setting Operation Arguments
  
• Executing Operations
  
• Extracting Operation Results
  
• Disconnecting from the Server
  
• Managing the Thin Client Cache
  

Thin client programs must include the header file <ostc.h>.