BUG: Custom Property from Provider of Type adIDispatch Fails

• ActiveX Data Objects (ADO)

SYMPTOMS

ActiveX Data Objects (ADO) does not correctly recognize properties of type adIDispatch. If your ADO provider raises a custom property of type adIDispatch, ADO does not correctly return the interface, for example:

   dim val as variant
   dim adoprop as adodb.property
   ...
   set val = adoprop.Value

RESOLUTION

There is no way to work around this bug within ADO. However, if you have created your own OLE-DB provider, you can get around this by raising the property, for example, as a column of a given recordset. In this case, you would bind the IDispatch to a column using the OLE-DB IAccessor::CreateAccessor interface, and then return that property via the IRowset:GetData method.

This workaround will work only if you have a custom OLE-DB provider and you have the source code for your OLE-DB provider.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

Given a custom OLE-DB provider that raises a property to the ADO Recordset object of type adIdispatch, this code may generate unexpected results for that property:

   Set adoprops = rs.Properties
   ' When Count is invoked, all properties are read from the provider.
   ' The IDIspatch interface incorrectly has it's default method invoked.
   for i = 0 To adoprops.Count - 1
      set adoprop = adoprops.Item(i)
      'For the custom property, the type is correctly returned as
      ' 9 (DBTYPE_IDISPATCH)
      adotyp = adoprop.Type
      ' May generate an error as default method the interface is returned,
      ' rather than the actual interface
      set val = adoprop.Value
   Next i

Keywords          : adoall ado10bug
Version           : WINDOWS:
Platform          : WINDOWS
Issue type        : kbbug