[thelist] Need to add a serial number system to my ASP script.

[Craig]

> > Yes my only aim (at the moment) is to prevent people using the DLL
without a
> > valid serial number.  I haven't really thought about piracy, or people
> > sharing the serial number with their friends.  What I would do is keep a
> > database of serial numbers I send to customers, and if I see a
particular
> > serial number on a piracy site (etc..), I guess I would try to take
action
> > against the customer, or at least not provide any future versions of the
DLL
> > to that customer.  This is only a quick explanation, but can you see any
> > problems I might encounter doing it this way?
>
> Um - how is the dll going to know what a valid serial number is? (I
> suppose you could have a list of hard coded values, or you could
> recompile the dll for each customer...)

Yes I see your point.

Compiling for every customer might be a good idea.  If I had a "good copy"
of the VB6 project, and only changed one line for the serial number, then
compiled it for that customer, this might be the best way.  I may be able to
automate the line change and compiling, to make things quicker.

Thanks Ken! :)

On a side note, do you know if it's possible to do a "response.end" in a
ActiveX DLL?  I can get response.write and everything else working, but
response.end doesn't seem to "end" the script processing, and it continues
on.

Regards,
Craig Dyer