You can put forms in a DLL and call them. There's no
limitation.
    For restriction: Somewhere on MSDN there's a page
about how to make a control licensed, the same way
that VB controls are licensed and can't be run otherwise.
I don't have a link to it, though. Another option might be
something like a dummy parameter. Your DLL parameters
can be seen in an object browser but that doesn't explain
them. So besides the natural difficulty in figuring out how
to call a function given object browser info., you could also
make it more confusing by adding a dummy parameter,
naming the parameters in a vague way, etc.

--
--
Visual Boodu .NET  wrote in message
news:VQCtc.14455$L.3107{at}news-server.bigpond.net.au...
> Is there any way I can prevent people using my DLLs in their programs?  I
> mean, I'm new to making DLLs and I'm guessing that if I can reference my
> DLLs in my projects then there is nothing stopping anyone else from
> referencing my DLLs in their projects.
>
> Also, Just wondering whether there is a type of *thing* which is like a
DLL
> but includes a form as well.  I want to include modules in my app, so say
> for example purposes my app contains a main form and a calculator module.
> The main form is the exe and the calculator gets called from a separate
file
> when needed?  Any ideas?
>
> Thanks for the help.
>
>
---
þ RIMEGate(tm)/RGXPost V1.14 at BBSWORLD * Info{at}bbsworld.com

---
 * RIMEGate(tm)V10.2áÿ* RelayNet(tm) NNTP Gateway * MoonDog BBS
 * RgateImp.MoonDog.BBS at 5/28/04 9:50:05 AM