[ActiveLock-Users]Activelock 2

[Dick <d.k...@bi...>]

Hi,
I have been using Activelock for a few years since version 1.5.
I have come across a problem with 1.84 and so I have now just discovered =
and downloaded version 2.

One of the problems I found with version 1.84 was that it would easily =
get mismatched with a project (Active X component can't create object =
error). This situation would come about by me simply upgrading to a new =
pc. Copying over all my files and recompiling a project. I would need to =
recompile the Activelock OCX again which would seem to change is =
compatibility. I would then need to issue a new install when upgrading =
users to the latest version of my app to get back compatibility. This =
could stuff up anybody else's application that happened to use =
Activelock 1.84 on the same pc.

I assume that with version 2 now that it is a dll with binary =
compatibility set that I won't get this problem. That is unless I was to =
reset it's compatibility to project and recompile it. If I then issued =
it as part of my app would it not stuff up any other application using =
the original version?
If this is so I then also run the risk of someone else doing the same =
thing (accidentally maybe).

Can Activelock2 be recompiled with a different name (a name of my =
choosing) to help secure against this?
Could the code for Activelock2 be added into my application so that I =
don't even have to worry about compatibility with DLL's? If so how would =
I do it? Would this also improve security at the same time?

Hoping you can help.

P.S. I secure my apps by using Activelock to generate user codes and =
Armadillo for the time limit feature.

Best Regards
Dick Knighton
H & R Resources
www.raksolutions.com