Porting from VB3 to VB 5

[tmcconne]

I'm looking for guidance or references to help me with porting an application from VB 3 to VB 5.<br>
<br>
What problems are there besides 16-bit custom control replacement (.ocx for .vbx)?<br>
<br>
Thanks,<br>
<A HREF="mailto:tkmcconnell2@prodigy.net">tkmcconnell2@prodigy.net</A>

 

[Alt255]

The only problems I've encountered porting from VB 2 to VB 6 (assuming a kinship to your problem) have been the VBX to OCX problems (don't waste the company's money; plan on many hours for a major rewrite) and the inevitable incompatible file format. VB 3 may write in a format readable by VB 5 (I don't know, have never worked with either) but, if it doesn't, load the projects with VB 3, save all as text and then try to load with VB 5. It works with v2 and v6.<br>
<br>
Good luck from the trenches.

 

[MikeLacey]

We ported a, quite large, application from VB3 to VB4 (32bit).<br>
<br>
The basic method was:<br>
<br>
1) Save the form as text<br>
2) Identify each VBX and its replacement OCX<br>
3) Create a test form, and save it as text, for each new OCX so that you have examples<br>
Repeat<br>
&nbsp;&nbsp;&nbsp;&nbsp;4) Edit the original form, replace the VBX definitions with the new OCX definitions.<br>
&nbsp;&nbsp;&nbsp;&nbsp;5) Load the edited original form using the new version of VB.<br>
Until FormIsErrorFreeAndWorksOk()<br>
<br>
It's not much fun I'm afraid.<br>
<br>
Mike<br>
<p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>

 

[chiph]

Like Mike said, it's not much fun. One of our guys is looking at porting one of our products from VB4-16bit to VB6, and he comes in my office regularly saying &quot;What about this?&quot;, and my answer is almost always either &quot;Doesn't work in 32-bit land&quot; or &quot;Tell the boss you need to re-write it, borrowing snippets of code as you go.&quot;<br>
<br>
Chip H.<br>

 

[bvoelp]

It's been a few years, but I remember a &quot;Migration Wizard&quot; of sorts that was a tremendous help moving a very large commercial VB3 app to VB5. It only took us about a month to fully release the VB5 version. The VBX to OCX worked fairly well, as I remember. The only requirement was that you had have the companion OCX installed and that the pointer file was set up to tell the wizard what VBX's matched what OCX. The biggest problems was with third party VBXs. <br>
<br>
I believe this wizard was on the CD somewhere in the tools folder. (I can't find my VB5 CD, or I would provide the extact location and name). The MSDN Online Knowledge Base is sure to still have the Q article on the subject.<br>
<br>
All the other responses are very accurate, in that the files need to be in text format, and you should keep a copy of the originals to refer back to, for those situations where the migration didn't come across clean. <p>Bruce Voelp<br><a href=mailto:bvoelp@if.rmci.net>bvoelp@if.rmci.net</a><br><a href= > </a><br>Earn AS in 1976 and BS in 1986. Learn to talk with computers when the only interface was 80 column punch cards, and paper tape.

 

[culshaja]

I've ported quite a few programs from VB3 to VB5. The only problems I have had is when the older projects have used the Sheridan 3D controls and the MicroHelp gauge control. When I realised that these where on the Tools directory of the VB5 Enterprise CD and then installed them most of my problems have gone away. Only syntax differences between the older grid controls and the newer pose problems and these are easily found and changed.<br>
<br>
<br>
James