Ssomewhere in my misspent youth, I skipped VB3, and do not rember much of what it is/was like. I have just been invloved in the conversion of a VB Dos (VB 1.0?) program to VB6.
The largest part of the conversion really ammounted to a formidable set of 'search and replace' functions. I just built a table of OldFunction NewFunction names and 'list' of the objects in the app. Programmatically, I 'read' each of the objects, parsed the line for the "Old", and If Fouond, replaced it w/ "New". I got approx 98% of the conversion with this. It would at least 'run'. There were a few items which I could not see any direct replacement. In these instances, I just commented out the code and added a line "STOP". This made it 'easy' to see what the program was really doing at the point where the problem(s) are.
This problem was probably more involved than yours, as I also needed to include the conversion of the database from a flat file data set (individual tables) to a relational database. I did that part in two steps, one with the program conversion, which translated the individual table accesses to UDT Class modules. this helped to Isolate the db functions. The actual change to a relational db is (as of now) still incomplete. If they ever get more funding, I'm supposed to go back and finish the job.
MichaelRed
redmsp@erols.com
There is never time to do it right but there is always time to do it over
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.