>>>>>Hi Matt,
>>>>>
>>>>>Keep in mind that if you use NEWOBJECT instead of CREATEOBJECT you would never need to use SET PROCEDURE TO, which for me is better.
>>>>
>>>>Hi Huga
>>>>
>>>>There can be quite a performance difference avoiding CREATEOBJECT. :)
>>>
>>>That's true, but I consider using NewObject() a best practice, so that I never have to worry about whether a classlib is visible. To me, it's the same as using IN everywhere that it's accepted.
>>>
>>>Tamar
>>
>>Hi Tamar
>>
>>I agree with the IN clause. I see m. where accepted as a best practice too, but not everyone agrees. I would prefer an approach that is not as slow as newobject.
>
>FWIW, I'm pretty sure IN has a speed penalty, too, but given the speed of today's computers, it's a cost I happily pay to be sure my code operates as expected.
>
>Tamar

Agreed.