activex control licencing

vb doesnt have that much control over the licensing of its activex components.

we are kind of stuck with teh default built in implementations, you could probably achieve implementing these yourself with alot of work and research, but I havent seen anyone move in that directin with vb yet.

vb built in license is a go / no go type. the only setting is to require license in your compile options

when it is set, a license is required to even load it in design time. its basically just a setting that is stored in the registry that the ole compoenents check when they instantiate your control in the ide. this license string is then compiled into your app and supplied when your exe calls the ocx (so it can probably be extracted from the exe as well)

sorry dont have anymore info on it...if you google it there are some resources though telling about how the default mechanism is weak.

outside of the default mechanism you could come up with your own code that you put in teh initialize events or something...but those woudl likly require the developer to distribute some other info with thier exe..which isnt bad..just more work for you. and something they can messup and come to you for support on