• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 336
  • Last Modified:

sysinfo.ocx

I am writing my first VB program and regularly have Visual Basic turn it into an exe to see if it runs as an independent program.
I thought everything was fine, but if I transfer my program to an other computer - with no Visual Basic installed, it just won't run.
I get a message "SYSINFO.OCX or one of its components missing".
What does this mean ?
0
michelvanpassel
Asked:
michelvanpassel
1 Solution
 
OtanaCommented:
You're probably using an ocx in your program that has not been installed on the other computer.

Did you add any extra components to your program?

TO avoid this, you can use the package & deployment wizard to create an installation package that includes all necessary files.
0
 
kdg2000Commented:
If you will transfer EXE on other computer, it(he) in any case will produce an error, as it is required VB to programs written on run-time files:
 Msvbvm60.dll
Stdole2.tlb
 Oleaut32.dll
 Olepro32.dll
 Comcat.dll
 Asyncfilt.dll
 Ctl3d32.dll  

If you except for main use of components additional, it is necessary to place(install) and them. For this purpose is necessary installation package (Package and Deployment
 Wizard).
0
 
WolfgangKoenigCommented:
You need to copy the file "SYSINFO.OCX" to the
system32 directory in your destination system ...

WoK
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

 
WolfgangKoenigCommented:
When your destination system don't have the file:
Msvbvm60.dll (VB6.0 virtual machine)
you have to copy this file too to the system32 dir

WoK
0
 
TimCotteeHead of Software ServicesCommented:
Or to simplify the whole procedure, run the packaging and deployment wizard to create an installation package which includes all the required runtime files and included components and can be installed on the target machine. This is the recommended way to install applications on other machines. The p&d wizard is not the only (or necessarily the best) way to do this but it suffices in most instances.
0
 
vindevogelCommented:
Like TimCottee says ...
If you're putting a VB exe on a client, make a setup with the package & deployment wizard.

Don't bother about finding the Dll's yourself, you'll always miss out one or more...
0
 
michelvanpasselAuthor Commented:
Thanks Tim.
But also thanks to the others who gave the same advice.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now