>>>>I have created an automation server that will be used in VB apps. When browsing the object descriptions come up for all of the VFP intrinsic methods and properties, but not for the ones that I've added. Is there a way of adding my own descriptions?
>>>
>>>Just a comment, by making all the default PEMs for an object PRIVATE they shouldn't show up in VB, if you want to clean it up a little bit. I hope that wasn't a VFP7 thing too.
>>>
>>>Thats why alot of people use the Session class for COMs, less PEMs to hide.
>>
>>

>>I'm actually doing just that, using the Session
>>class and making the unneeded default methods
>>PROTECTED.  I made what *has* to be *the*
>>rookie move though.  I made the ERROR() method
>>PROTECTED.  This, of course, has the effct of
>>
>>ON ERROR RETURN .T.
>>
>>...dupid, dupid, dupid..
>>
>>Is there a way of hacking the type lib to
>>include the information?
>>
>>

>
>No, you need to generate a new COM Server - making the PEM public changes the interface, which would really require assigning a new CLSID; not doing this would break anything that used early binding, since the VTable, resolved at compilation time with early binding, becomes invalid.

I actually went in and temporarily disabled the 
error handling.  What I meant was, is there a 
way of hacking the tlb to insert property 
descriptions?

   ...kt