Article ID: 201826 - View products that this article applies to.
This article was previously published under Q201826
When you use ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX) and try to access properties in the Properties Collection, you may receive the following error message:
The following error is returned from ADO 2.5 and later:
Run time error '3265':
ADO could not find the object in the collection corresponding to the
name or ordinal reference requested by the application.
Run-time error '3265':
Item cannot be found in the collection corresponding to the requested name or ordinal.
The object's ParentCatalog property was not set to a valid Catalog object,
the ADO Connection object associated with the Parent Catalog may be invalid.
Set the object's ParentCatalog property to a valid Catalog object,
make sure the Parent Catalog is associated with a valid ADO Connection Object.
The 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
The 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.
Article ID: 201826 - Last Review: August 23, 2001 - Revision: 1.0