Category name or ID (as returned from RegisterCategory). This may be VT_EMTPY or zero, to indicate objects not part of any category.

Name of the McObject sought. The name may have “dot” syntax if the item is a child of some other object and it may use the "double colon" syntax for namespaces. Any “double colon” syntax will override the effect of the bstrNamespace and eLookupMethods arguments (below). If a namespace is specified by the “double colon” syntax then it must match exactly. If a parent is specified without a “Namespace::”, then it is looked up using the same namespace rules as for the target name (see below).

VARIANT [in, optional] The parent object, or if missing (VT_EMTPY, VT_ERROR or VT_NULL) or a NULL pointer, then only an object with no parent is found.

is supplied, then the default lookup method is mcobjMatchExactNamespace.

mcobjNamespaceMatchMethods [in, defaultvalue(mcobjMatchMethodDefault)] The default behavior (0) differs depending on whether bstrNamespace is given or not. If no bstrNamespace argument is supplied, then the mcobjMatchScopedNamespace method is used with the default Namespace property as the target namespace. If a particular

Default match method. This varies depending on whether an explicit namespace argument is supplied. For Item lookups, or for the SetEnumFilter or GetCategory_NewEnum methods, if no bstrNamespace argument is supplied (i.e, it is NULL or empty), then the mcobjMatchScopedNamespace method is used with the default Namespace property as the target namespace. If a particular target bstrNamespace is supplied, then the default lookup method is mcobjMatchExactNamespace.

The target namespace must match the object's namespace exactly.

The object's namespace needs to match the target only up to the length of the the stored object namespace string. However, if there are multiple such objects, the one with the longest namespace string is returned as the matching entry. Example: target namespace "ABC::": objects with namespaces “ABC::”, “AB::”, “A::” or “::” match in that order of precedence. Objects with namespaces “ABCD::”, “ABX::”, and so on do NOT match.

The object's namespace must match the target namespace only up to the length of the target namespace (which can be empty for lookups with any namespace). If more than one matches, then the one with the shortest namespace (i.e, the most “global”) matching up to the length of the target is prefered (or the first one if there is a tie). This lookup can be used when you have some name and a namespace and you wish to find some object of that name which is within the namespace or a deeper one. Example: given a target namespace of "ABC::": objects with namespace “ABC::”, “ABCD::”, “ABCDE::” and "ABCE::"all match, in that order of precedence. Objects with namespace “AB::”, “A::”, “XYZ::”, and so on do NOT match.

The object's namespace is ignored in the test. For Item lookup's, this is equivalent to specifying a global ("::") target namespace with the mcobjMatchAtLeastNamespace lookup method. For SetEnumFilter or GetEnum methods, no namespace filter is applied, so objects with any namespace are enumerated, so long as they pass the other tests.

A mask for these values.