- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsDear all,
I need to migrate on old VB4 16bit application to VB6.
When I open up the VB4 project file, I got error messages that the following OCX files could not be loaded: THREED16, CRYSTAL16 and GRID16. I checked the window system directory, but all three files are there. Do I need to specify the path where the OCX files should be loaded from?
Subsequently I receive error message that forms could not be loaded because controls are missing, what is not a suprise because VB just did not load the OCXes, right?
Many thanks in advance for your help
Joc
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: EnladePosted on 2004-12-29 at 11:23:13ID: 12921316
This is more likely NOT a problem with converting from VB4 to VB6. It looks more like you do not have some of the controls installed on your development machine that that older source needs (Threed16, etc). In any case, you probably don't want to be using old controls anyways. So, create a copy of the VB4 application and go ahead and load it clicking OK for each screen that pops up during loading. Then close VB6 and take a look at each of the .LOG files that get created due to errors loading the VB4 forms. Make note of all of the controls that are giveing you problems and for each control you will need to find a comparable newer control. Then you need to load the project again and on each form that had errors replace the existing control (old control), or rather the dummy label that gets tossed in its place, with the newer control. Then you need to go through each of the new control properties and modify them to be similar to the old settings (you can look at the original VB4 form code in notepad to see a lot of the settings for those older controls). Then you need to adjust any events that are not supported by the newer controls. If you picked your new controls well then you will not have much to change. There are also some tricks you could do by editing the VB4 source in notepad (replaceing control references directly), but that is harder to explain.
After you get all the controls replaced and made some adjustments to accomodate the newer events in the code then you can try to compile the code to see what syntax errors exists. But your first step is to get the code to load properly with all the controls that you need.