Moving VB6 Project to Different Computer

Hello,
I'm trying to move a VB6 project from old computer to NEW muscle computer... both are XP Pro.  VB6 is installed and runs fine on both...

On OLD computer, I have directory structure like:
Shared Docs
- ProjectSource
--FolderOfControls

where the folder containing user controls is inside the project source folder... I tweaked the names above a bit to be clear...

On new computer I have to put the source under C:\SomeOtherFolder and when I open project it can't find certain user controls even though they are there in same folder as before...

I looked in the .vbp file to see if there was a hard coded path to the controls but did NOT find any... just refernces to the controls via the folder name...

How do I xfer this project to new computer and fix or eliminate these issues????
Regards,
-Tim
torrid333Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

torrid333Author Commented:
Follow up... it said I was missing TABCTL32.OCX and I noticed it was not in system32 on NEW computer... so I moved it there and successfully REGISTERED it in windows...

I still get same error when I open the project... it's trying to open the TABCTL32.OCX file from the source code folder... says it can't load it... does not seem to load from Windows area.... very odd but I say NO to continue loading project...

Any ideas appreciated.
0
biztigerCommented:
I think there is a problem in registering the activex TABCTL32.OCX. Also it will be great for troubleshooting if you post the .vbp file.

Do you use the following command for registering the control:
regsvr32 yourcontrol.ocx
0
Antagony1960Commented:
TABCTL32.OCX is the MS Tabbed dialog control which is hideous looking (it's sooo Windows 3.10) I'd consider replacing it anyway. Either with the Tabstrip control--which can be found in the "Microsoft Windows Common Controls 6.0 (SP6)" bundle--or with a decent 3rd party tab control.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

torrid333Author Commented:
I don't even think I use that control to be honest.  I switched to a much nicer control awhile back...
I don't see it in the .VBP file though.

Maybe I should let the project load anyway even after the error?

0
Antagony1960Commented:
The reference would appear near the top of the vbp, something like this:

Object={BDC217C8-ED16-11CD-956C-0000C04E4C0A}#1.1#0; TABCTL32.OCX

It could also exist in one of the project's forms.
0
HooKooDooKuCommented:
The biggest problem moving a VB6 project from one machine to another is all the dependancies.  What can really mess you up is when the dependancies have been updated such that the registry number stored in the VBP on the new machine doesn't match the registry number stored in the VBP from the old machine.

What I have found necessary at times (especially when the dependencies are VB DLLs that we've created with frequently changing registy values) is to try to start a new project on the new machine and add the dependancies to this new project.  Save the new project.  Then use a text editor to copy-n-paste the signature of the dependancies as recorded in the new file over the matching dependencies in the old file.  Then you should be able to open the old file on the new machine without any errors (assuming you can find all the dependencies).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
torrid333Author Commented:
Turns out I was not using the TabControl but there was a reference to it in the project.  I went through the project and examined everything under Components and References and removed anything I did not think I was using.

I then RECOMPILED.  THis was all done on the OLD computer.  The recompile verified whether I removed anything I should not have.

I then moved the project folder over to the NEW computer.  Opened it and NO ERRORS.  Because all of the component references were already on the new computer under windows\system32.  

Thanks for the suggestions. I should have done this a month ago but thought it was going to be a lot more complicated.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.

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.