>If you really want to do that, keep all your code in a class and subclass it. But whomever you are supposed to be working with won't have access to the methods in your class.

The very problem with classes being not shared or even sharing it as readonly is that not every member of the development team could use it in setting default forms or in mapping fields. That said, it breaks the essence of OOP methodology.

>
>>>Can I protect my code in the classes so I can give them to another
>>>VFP programmer, who is going to work with me, but I do not want He can see or modify my code?
>>
>>I do not know your reason of not sharing your classes totally because the very essence of OOP is REUSE. In anyways, why not trying to separate the subdirectory of your classes and share it as readonly. I haven't done it myself so to speak because all our classes including our framework are 100% shared to every member of the development team.
>>
>>>What I need to do... I don't know!
>>>AnyBody can help me?
>>>Thanks.