A kind of dodgy way around it would be to create an olepublic object with all the properties that you have hidden then have in your code something like this

LOCAL MyObject AS MyCom.MyClass

MyObject = CREATEOBJECT("MyOtherClass")

Then MyObject would have the IS without all the PEMS that you don't want to see. One fairly big problem with this would be that you would have to keep the com object up to date with any changes made to MyOtherClass.



>Bummer. It sure would be nice if they didn't show. Makes it hard to create a business object that only shows it's properties and not all the base class props that are meaningless and unused in that context.
>
>AFA VS, I did a test in VB and a protected prop doesn't show in IS, or am I missing something.