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

transfer my vb6 project to another computer

I had vb6 on one computer and now I installed vb6 on a second computer but I run into errors when I take the project and open it on the new computer.  Is there a way to open the project or back it up properly in order to use it on another computer?
1 Solution
Martin LissOlder than dirtCommented:
What process did you use to put the project on the new computer?

What problems are you having?
I have not ever had issues taking the whole solution folder to a new computer, then opening that solution on the new computer.

Is VS the same version and patch level?
Do you have the same rights on the new computer?
Can you be more specific on the errors you get?
Onn LightSAP Technical ConsultantCommented:
Dear  al4629740

One way of doing this is by creating a setup for your project, if you have VB setup toolkit installed you can use that, there are other setup programs (Installshield, Setup Factory etc) for VB6 also available but i doubt any are free.

If you don't have a setup creator available, the manual way of doing this is through noting down all the References and Controls of your project and moving those dlls, ocx etc to the target machine (if they do not already exists there) and registering them with regsvr32, so that when your project loads on the target machine it find the correct references and controls.

Always start VB 6 with Administrator privileges so that it can update the registry as required.

These are just the things that come off my mind, but they should work.

Be warned regsvr32 updates the registry and any registry update has the potential to severely affect the system, so make a restore point or a system backup ready.

Thanks and Regards
Sounds like a classic situation where your VBP references a control or other object that is installed on the primary computer, but not the secondary computer.  This will also happen if the control is installed on both computers, but the version number is different.

You'll simply have to track down which control is missing or is the wrong version.  The easiest way to do that is to open the VBP in notepad to see what controls are included.  Then try to rebuild a VBP on the secondary machine adding each control listed in the primary VBP.  Once you've got all the controls added to the new project on the secondary machine, save it and then open it in notepad as well.  Then you can compare the details in the two VBP files to see which control is your problem.

Keep in mind, this problem can occur because either the GUID for the control is different, or even if just a version number listed in the VBP is different.  The one part you can ignore is the PATH to the control the VBPs will list.  One might have relative paths, the other fully specified paths.  But the exact Paths are not important.  The GUID (16 digit hex number) and version numbers are what are important.

If you want, you could post a copy of your VBP (as it looks in notepad) and we can talk you though some of these details.
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