OCX, What files are needed to Register one?

Run the Package & Deployment wizard. This will create a CAB file that you need to distribute. Also, a file (called Setup.Lst) will be created telling which files are required.

I do not have the code for the OCX, but it is part of another programs setup.  I do have the lic file, the OCA file, and the OCX, but when I try to register it, I get the following error..

Load Library(".....OCX") failed
GetLastError(0X00000485).

Thanks,

Rog

Do you have .DEP (dependancies) for this file? If you have one, open it (this is a text file). It says everything needed by the components.

You could also create a dummy new project and only include this control in this new project. Then use PDW to see what files are included in the Setup.lst.

I don't have the DEP for that file.

I tried to make a dummy project with this OCX, but could not put the OCX on the form/Toolbox as it is not registered correctly.

Thanks,

Rog

You wrote: «When I run the set up program it will register.»

Don't you have it correctly installed on at least one computer?

Sometimes these will not install
if you dont have the runtimes..
I find this to be true more with
..dll files than .ocx..but you never know.
make SURE the appropriate vB runtimes are installed

I cannot give points to just comments added to the answer area.  I do appreciate those comments though.

Rog

Hey Rog, you read my last question/comment?

Don't you have it correctly installed on at least one computer so you can create a dummy application from there?

Also there is a dependancy wlaker that comes with VB that can help you find which other files are needed.

Well I thought I did.  The control will register via the regsrv32, but I cannot pull it into my code (Add to control box).  VB 5.0 gets a bad error, something about Kernel32.dll and closes.  I am looking to the vendor of that OCX to see if they can provide some help.   DARTDSP.OCX.

Thanks for your suggestions,

Rog

When you install the product on your development box a dependency file is also supplied. This file lists all the supporting files (DLLs etc.) and it also explains whether these have to ve registered are not. This should be there on your box, since you have done it once correctly.

FYI...
In fact, VB6 package & deployment wizard uses this file to get the information. When it does not find, it prompts you to mark this file as no dependancies.

Hope this helps you.

Cheers,
Ravi