VB 3 to VB 6 1

[AZED]

How do you convert VB 3 programs to VB 6

 

[Karl Blessing]

just open the VB3 project in VB6(if it isnt saved in binary format) and Vb6 should say something like do you wish to conver this to VB6. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href=

http://kb244.8m.com>

</a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)

 

[NickBulka]

That will get you started.&nbsp;&nbsp;However, if you're using any VBXs, you'll need to acquire the corresponding OCX.&nbsp;&nbsp;Also, if you're using the Windows API,&nbsp;&nbsp;you'll need to convert from 16 to 32 bit.&nbsp;&nbsp;There are also some other possible problems.<br><br>When VB4 came out, Crescent software published a wizard that helps convert VB3 applications to 32 bit VB4.&nbsp;&nbsp;If it's still available,&nbsp;&nbsp;I'd use that first.&nbsp;&nbsp;If it can't convert, at least it identifies the problem area.<br> <p>nick bulka<br><a href=mailto:nick@bulka.com>nick@bulka.com</a><br><a href= > </a><br>

 

[steveblum]

Once you open the project, it is likely not to run correctly, if it is a project of any complexity at all.&nbsp;&nbsp;The following are some of the issues you may need to deal with:<br>1. Any custom controls used in vb3 will be VBX 16-bit controls.&nbsp;&nbsp;These won't work under VB6.&nbsp;&nbsp;They'll give you errors when the project loads and when you open the affected forms.&nbsp;&nbsp;VB6 will turn them into picture boxes.&nbsp;&nbsp;Then you'll have to decide what control to use instead and set about inserting that control.&nbsp;&nbsp;This can be trivial or complicated, depending on how much code was specific to the way the control worked, and how much event code was written.&nbsp;&nbsp;This was a huge effort on a project I converted from vb3 to vb5 a couple years back, because the vb3 project used Sheridan grids and listboxes all over the place, and the new Sheridan 32-bit controls were VERY different and did not provide automatic conversion.<br>2. Any API calls will have to be modified.&nbsp;&nbsp;In general, all integers in 16-bit API calls are now of type long in 32-bit API calls.&nbsp;&nbsp;Also the name and or alias of the API call is different.<br>3. If the program did any database access, you will likely need/want to convert it to use the newer database access technologies, such as ADO and OLE-DB.<br><br>Hope this helps.