Hi!

Its by deduction.
Custom class is preferable because it does not contains any additional functionality when initialized. You can reduce the amount of data transferred when remote COM object initialized by hiding all defailt PEMs of object in the Class Info dialog box -> Class PEMs editor dialog box (when opened from class info, you can change visibility of default PEMs there). That is also a reason why I said to use hidden property to store reference to timer object ;)

>>Hi!
>>
>>COM objects are quite different than usual VFP objects. It is not recommended to use any other class than "custom" for COM objects.
>
>Vlad,
>Why do you say this? Did you read it somewhere or is this by deductive reasoning because you have had problems with other classes?
>
>FWIW, the number 1 recommended class to use for COM objects these days (post-SP3) is the session class. There are fewer exported PEMs so it makes for better performance in late-binding clients.