If someone created a class with a property named Count, I wouldn't care what kind of results their class gave me ;-) That would probably be the tip of the iceberg as far as unexpected behavior.

>James,
>
>If oProperty was a pointer to an object that happens to have a Count property you'd get a false positive of it being a collection.
>
>>Would the following work to distinguish between arrays and collections?
>>

>>lcProperty = 'oObject.oProperty'
>>Try
>>    lnCount = eval( lcProperty + '.Count')
>>    * Collection here
>>Catch
>>   * Array here
>>EndTry
>>