Automatically register ActiveLock.ocx on the users computer

How do I get the activelock.ocx to register automatically on the users computer with VB6. I downloaded activelock from http://www.activelock.com. This is a great active x control to limit an app usage in time.

When I installed it, I run an Install.bat file which opened a DOS session or I could have run

regsvr32 c:\windows\system\nslock15vb6.ocx

from the start menu after copying the ocx to the system folder. But I don't really want my users to see or do that. I could run the aboce expression easily but then you get a confirmation from Windows that pops-up and this is annoying.


Is there any way to do it transparently?

Thanks in advance.

Atchoum

something called a set up file well do that for you. Like you can use Package & Deployment Wizard that came with vb to to make it, or you can use Install VISE and use the wizard for Visual Basic prodects and it well look for all of the dll and ocx files that is in your program. Doing eather ways, it well register that ocx file.

That's what I thought. But it did not work. I tried it on another computer.

Is it because the ocx has no dependency file. (That's a message I got when I packaged it) or this has nothing to do with it?

Thanks,

Atchoum

what did the error message said?? If I know what it said then I can help you some more

It probably has nothing to do with the OCX. I installed it on another computer and got this error message:

Run-Time Error 380
Invalid property Value

I don't get this error when running from VB only from the installed app. On the other computer I get a different message about the resource file but it is in French that's why I did not know what was going on (I am French but I am confused by messages in French, figure this out).

Atchoum

I think I know what your problem is, but I'm not sure. all I have to say is to see if you are using any other ocx and/or dll files in your program, and if so to add it to the set up program.

I've got an app using ActiveLock (GREAT program!!) and I use the standard P&D wizard.

I've never had to worry about specifically registering the ocx.

Do you get the error during design-time or only at run-time after compiling to an exe?

i just got it. Just lost 2 hours with this. :mad:

There was a problem with one of the forms, which seemed to not have been in the proper directory or the form that I was using add the same name but was actually in a different directory. Whatever... I just saved the form to the app directory and repackaged it and it worked.

What a stupid mistake. Thanks for reassuring me on OCX. Sorry to have bothered you with this.

Have a great day.

Gilles