|
-
Jan 4th, 2004, 11:23 AM
#1
Thread Starter
New Member
System Error &H8007007E (-2147024770)
Hi there.
I have a user who keeps getting this error when they run one of my programs.
System Error &H8007007E (-2147024770)
They are using XP Pro, and i have never seen the problem before
I have searched google, and found that it could be due to an incorectly registered dll.
It is a small program consisting of no more than a form, text box, couple of command buttons and the winsock control. I think that the problem could be down to the winsock.
Anyone have any ideas??
Thanks!
-
Jan 4th, 2004, 11:30 AM
#2
Kikin
How did you deploy your app? What did you use? etc...
-
Jan 4th, 2004, 11:38 AM
#3
Thread Starter
New Member
I just gave out the EXE at first, as i assumed they would have the VB6 dependancies already there.
It appears the microsoft does not include the winsock control lol. The users who didn't have it, i gave the winsock OCX as a seperate file and told them to stick it in the same folder as the exe. This worked for everyone, except this particular user (who now has the exact same error as he did before). The errors being the same made me think that it was the winsock control which was the prob for him.
Thanks!
-
Jan 4th, 2004, 11:43 AM
#4
Fanatic Member
you should
use a software packaging solution, such as INNO Setup, or the standard Package and Deployment Wizard which comes with Visual Studio.
DLL's and OCX's including Winsock, have to be registered using a system command, REGSRV32
these packaging solutions bundle up all the needed controls, which can include the vb runtime dependancies, and register all of them on the end user's pc.
Most prefer to use INNO, as I do myself.
-
Jan 4th, 2004, 11:47 AM
#5
Thread Starter
New Member
Yes, i use it, but i didnt see the point for just 2 (at the time - now 50 lol) users and a 10kb exe
Can the winsock OCX file be taken straight out from my system folder and registered on the users machine? I will probably register it manually.
Thanks!
-
Jan 4th, 2004, 12:12 PM
#6
New Member
may be it will be ok if he copy the winsck.ocx to windows\system32\ or winnt\system32
-
Jan 4th, 2004, 01:03 PM
#7
Kikin
First major rule in programming and deployment.
Don't take shortcuts just do it correctly.
You will have less headaches that way (unless egg on the face suits you).
Use ********** and Inno Setup to accomplish your task. See bottom of post and look here for more info: http://www.***********/support/support.htm
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
|