Project referencing to a local OCX...

[SilverTab]

I tried to make a package of my app with the package&deploy wizard..

However, it seems like my app is referencing to a local ocx (MSWINSCK.OCX)


The thing is, I wanted to add the winsock ocx as a reference (not a component) so I can use it in a class...since I couldnt find it in the reference list, I just searched my HD for mswinsck.ocs and I added it to my app directory....and added it via References >> Browse...

the problem now, is that, the project isnt referencing it as a relative path (i.e. app.path/mswinsck.ocx) but as an absolute path.. ( C:/My Programs/blah.../mswinsck.ocx)

so obviously, if I try to send my app to someone else, he gets a runtime 429....


Im trying to change that, but I cant see where the reference is made...I checked out Project >> References, but nothing related to winsock is checked...

where can I fix this?? Any help would be appreciated! How can I set my project so the OCX is loaded from app.path/mswinsck.ocx, and not using an absolute path???

[MartinLiss]

Moved.

[SilverTab]

Note: I could always add a reference to system32/mswinsck.ocx Im pretty sure it would work...

but how to I remove the reference to C:/myprogrampath/mswinsock.ocx ?? Its not showing anywhere in the references, and yet, I know its there since the Package&deploy wizard tells me it is...and I CAN create new instance of a winsock in a class...so obviously there is a reference to it somewhere....but ...where!

[SilverTab]

Ok I *think* I was able to use the MSWINSCK.OCX from system32...(I edited the .vbp file myself, removed the reference to the local ocx, and then I loaded my project, and added it via the Project >> reference...and it seems to have work)... still my friend gets an error 429...
(ActiveX component cannot create object)


The only thing I did pretty much was to add it via Project>>Reference...
it wasnt in the list so I Browsed to C:\WINDOWS\system32\mswinsck.ocx and the ocx was added...and i thought it would fix the 429 problem...

[randem]

Basically what Runtime 429 Error means is that you did not register the component before attempting to use it.

[SilverTab]

ok that's what I thought...

weird thing though, is that, I used a DLL info tool, and it said that mswinsck.ocx was registered....

Im out of ideas here.... could it be that its *another* mswinsck.ocx that is registered, and not the one in system32/mswinsck.ocx ???

[randem]

That could be the issue that you have two different versions on the machine.

[SilverTab]

ok...ill try messing with the OCX registration...try to figure out which ones are where, and which ones are registered....ill report back! :)

[randem]

Did your tool tell you where the registered one was located?