Microsoft doesn't know whats happening??
I have had this problem may times. It seems that when you install an
OCX it may or may not create the correct entries in the SWDEPENDS.INI
file. Check the help file for your OCX for "Distribution files".
Some files to check for are (OC30.DLL, MFCANS32.DLL, OC20.DLL)
I have had the same error message appear when OC30.dll was not on the
user's machine, and I did not distribute it with my app. Hope this
helps.
Quote:
>I have a similar problem with an OCX that comes with VB, COMCTL32.OCX and
>Thanks...
>> Check for previous versions of your OCX (search the entire hard drive
>> -- it's safer that way). If it is already there then blow it away and
>> reboot your system.
>> Also check for registry entries for your OCX and remove those. Make
>> sure you also get any of the CLSID's for your OCX. Also make sure you
>> search on whatever short names and identifying names it could possibly
>> be under in the registry. Remove all of these.
>> Then try reinstalling it.
>> ---------------------------------------------------
>> >I have created a program using a OCX not included in VB 4.0.
>> >I used the Setup wizard to create the setup files. When I
>> >try to install this program on another machine, I get the error
>> >"Not able to register the OCX". What is this?
>> >The registration works fine on some machines, but not on others.
>> >I have tried searching MS WWW, but no luck. Their description
>> >doesn't work (Adding some lines in SWDEPEND.INI). I have met
>> >other people with the same problem, but no one seems to know
>> >why this error occurs. I have also tried manually registrating
>> >the OCX using REGSVR32.EXE. No luck at all.
>> >The OCX does not require any DLL files.
>> >I am totally lost here. What should I do. Anyone who read this, have
>> >any idea what I could try? Microsoft doen't answer any questions.
>> >I suspect they don't know why this error occurs.
>> >Thomas
