The information in this article applies to:
SYMPTOMSWhen using ADOX and attempting to access properties in the Properties Collection, the following error might occur:
CAUSE
The object's ParentCatalog property was not set to a valid Catalog object, RESOLUTION
Set the object's ParentCatalog property to a valid Catalog object, STATUSThis behavior is by design. MORE INFORMATIONThe Properties collection associated with ADOX objects exposes provider-specific properties. However, ADOX objects can not expose this collection if there is not a channel for ADOX to talk to the Provider. This channel is created through the object's ParentCatalog property that points to a Catalog object. The Catalog object's Connection property must be set to a valid, opened ADO Connection object. Once this is in place, ADOX objects can expose any exposed provider-specific properties. Steps to Reproduce Behavior
Microsoft ADO Ext. 2.1 for DDL and Security and Microsoft ActiveX Data Objects 2.1 Library.
REFERENCESThe following is from Help under the ParentCatalog Property from the Data Acces Software Development Kit for use with Microsoft Data Access Components: Some data providers allow provider-specific property values to be written only at creation (when a table or column is appended to its Catalog collection). To access these properties before appending these objects to a Catalog, specify the Catalog in the ParentCatalog property first. Additional query words:
Keywords : kbADO kbADO210 kbDatabase kbGrpVBDB kbGrpMDAC |
Last Reviewed: October 5, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |