Kelvsat
asked on
Upgrade VB5 to VB6
I have a developed VB5 system and i would like to upgrade it into VB6 version. What r the special things i need to do for the upgrading process???
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
I had some "trouble" with some of the components (ms windows controls), where the library name had changed, but a simply "find/replace" solved that issue. unfortunately, I don't remember the exact names any longer...
CHeers
CHeers
Here is my suggestion:
After installed/ upgrade the VB5 to VB6, try open your vb project, go to Tools > References, check if some of the dll/ocx is missing.
Another method to see if your application is compatible in VB6 environment is try to run your program in a pure VB6 installed machine (No VB5 installed previously). Always See if some References is missing or not.
You may also find that some of the dll in References is missing, then try find out the greater version of dll in References.
After installed/ upgrade the VB5 to VB6, try open your vb project, go to Tools > References, check if some of the dll/ocx is missing.
Another method to see if your application is compatible in VB6 environment is try to run your program in a pure VB6 installed machine (No VB5 installed previously). Always See if some References is missing or not.
You may also find that some of the dll in References is missing, then try find out the greater version of dll in References.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
AlonHirsch, thanks for this clarification...
Note that the library name is used in the events of these controls by default, but could also be used explicitely.
CHeers
Note that the library name is used in the events of these controls by default, but could also be used explicitely.
CHeers
The code in your project is 100% compatible with VB6. To prove this, open a VB6 module/form in a text editor and see what version is referenced: VB5.
The only other issue is your object references, which will generally work exactly the same, although upgrades are available for some of them, as mentioned in some of the above comments.
The only other issue is your object references, which will generally work exactly the same, although upgrades are available for some of them, as mentioned in some of the above comments.
Most of the code should upgrade without any issues.
However, if you are using DAO or ODBC in VB5, you might want to consider changing to ADO. This is not required for the conversion, but could extend the 'life' of your project as ADO is now the supported data access method from MS.
I've converted several projects - large and small and have had no issues at all with the conversion.
HTH,
Alon