Jess,

There are plenty of controls that don't ship with the source code. For example, all of the ActiveX controls from MS.

Just because you can't change the intrinsic behaviour doesn't mean that you've "Broken OOP"! In fact, the best way to ensure reuse is to have a clean, well defined interface and NOT allow access to the internal methods.


>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?

Yes, there are a couple of options.

1. Compile the classlibraries into an encrypted APP and let the new person call them with NEWOBJECT().

2. Compile the class libraries and then open the VCX and strip out the method code. Note that you MUST do this on a COPY of the class libraries, otherwise you won't be able to change the code. Give the new person the VCX (and VCT) files that you've updated.

Cheers,

Andrew