To my knowledge, there are no tools for migration PB applications. We migrated an application from 4.0 to 5.0 and then 5.0 to 6.5 and then to 7.0.
What we will do is take a backup of 3.0 pbls for use if migration fails.
Open PB 80. Select the application object from your 3.0 pbls. PB will by itself prompt you that the versions and are different and will be migrated. Click ok, then it will try to migrate and give you a report of obsolete functions(not supported in newer versions).
You can make appropriate changes in the pbls.
Hope it works. Pls let me know if you are successful.
It is also depending on how you programmed in your old code. The more hard code you use, the harder to upgrade. For example, in your menu object, you call a window, and this menu is associated with a window, you then have a real problem when upgrade with new version of PB. PB will tell you your window object cannot be upgarde because of the older menu object when generating the window. And it will tell you the menu object cannot be generated because of the older window object when generating the menu object... the circle.
The solution in this case, is to export your object to a text file, and tempararily comment out objects, and late take out comment after successfully upgrade all objects.
Anyway, the hard code is always bad programming, should avoid as much as you can.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.