|
-
Jul 6th, 2000, 05:18 AM
#1
I have an app that uses the winsock as a reference(a reference to mswinsck.ocx), when i run that on another machine i get a 'ActiveX Component Cannont Create Object' error on the first line that creates the winsock.
Code:
Set [Object] = New MSWinsockLib.Winsock
I made a setup with the PDW, but it does not seem to help
-
Jul 6th, 2000, 08:07 AM
#2
Lively Member
Have you installed the winsock control on the other machine and registered it?
-
Jul 6th, 2000, 08:29 AM
#3
Yes, i even copied the file to the application path and used regsvr32 on it, it works fine when i use a winsock as a component but when i use it as a reference it wont work.
-
Jul 6th, 2000, 04:08 PM
#4
Lively Member
I see. I dont think include the winsock control as a reference only. It has to be included as a component. It doesnt have to actually be on a form for you to reference its type in code. Trouble I have had with it though, is that I couldnt instance of a winsock object at runtime. I had to actually had to have it on a form, and then load control in an array when I needed more.
-
Jul 6th, 2000, 06:07 PM
#5
If you reference the ocx you can create it at runtime, if you add it as a component you can't.
I've currently worked around it by putting the winsock on a form and i create a new instance of that form everytime i need a new winsock, but i really want a working solution instead of a work around ;(
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|