Hi Viv,

>Does that mean that the resulting file can be used just as if it were an ordinary VCX file and can issue SET CLASSLIB TO?
><<
>
>No. You get a COM dll which can be called from any app (VFP,VB,ASP,Word whatever). You *can* us this from VFP using 'CREATEOBJECT('dllname.classname') but if you don't need to expose your classes functionality outside of VFP then you don't need to build a DLL.

So is it more of exposing methods of a certain class? How about lets say I made a COM DLL for a plain textbox class, can I just drop that COM DLL (is that the right term?) on a form and it will work just as if it were dropped from a VCX? You see, I was wondering if I could make 'encrypted' VCX files wherein nobody would be able to see the code for the methods and properties. It may sound a bit 'selfish' but this is what a client of mine wants - just make 'encrypted' classes so no one else would tamper with it.

Thanks again and have a great day!
Dennis