Implementing this [idea] would require lots of recoding on your side...
Try having a boolean switch on your OCX, this is the variable you'll test if
a client can use the functionality of your OCX, add a function on your OCX
name it, for example, Register.  This function will have a password
parameter or anything like that to be authenticated by your OCX, if the
calling client pass the authentication, set the boolean switch to TRUE and
therefore enabling ALL functionality of your OCX.

Jojo

----- Original Message -----
From: "Manish Jain" <memanishjain@h...>
To: "professional vb" <pro_vb@p...>
Sent: Friday, August 23, 2002 3:15 AM
Subject: [pro_vb] Security of OCX


> Hello Friends...
>     I've created one OCX that I include with every executable file
>     what I want to do is ....
>     my ocx should not be available to other EXEs on the Machine...
>     but until now any exe (having a reference to the OCX) can use it
>
>     what should I do to make the OCX work for my EXEs Only and not for the
> others
>
>
>
>
> ---
> Visual C# - A Guide for VB6 Developers
> This book will make it easy to transfer your skills
> from Visual Basic 6 to C#, the language of choice
> of the .NET Framework.
> http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059
>
>