Implementing a Resource Dispenser as a COM Component

Resource dispenser interfaces exposed to the application are not required to be Component Object Model (COM) interfaces. This allows DispMan to be used in a process without initializing COM, for example, to support the ODBC Resource Dispenser.

A resource dispenser maybe implemented as a COM component. If a resource dispenser exposes an API (like ODBC), then the resource dispenser might only be a DLL accessed by the application via an import library (or using LoadLibrary and GetProcAddress). A resource dispenser may also be a COM component which an application accesses by calling CoCreateInstance. If the resource dispenser is an Automation component, then the resource dispenser may be accessed from Microsoft Visual Basic™.