Issues resulting from upgrading to VB6 from VB4?? 2

[Sheffield]

Does anyone know of any potential issues that may result from upgrading to VB6 from VB4?

MSDN didn't provide much help.

Thanks,

 

[MichaelRed]

Never did 4 ==> 6. Did 1 ==> 6. Mostly replacing obsolete controls. Comm stuff is all wrong, 16 bit => 32 bit. I did mine with a parse routine (actually a collection). Generally attempted to compile & run pieces. Where it broke, i looked at the "fix". Collected 'like' fixes in routines. After some were avail, lumped whole thing in a dir, ran the parse/search/replace routines, dumped output to 2nd dir, Tried the compile run trick (ovre and over) intil the new one would work.

Biggest single "magic bulet" in this approach is that the Source for ALL VB stuff is reeeally just plain text. Also note that the Version number is in EACH object - AND needs to be changed!


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over

 

[AndyGroom]

Biggest problem I had was with COMCTL32.OCX because I think Microsoft renamed it to MSCOMCTL.OCX and it was a pain in the arse, I had to edit all every form and every project manually because although VB6 would say "Do you want to upgrade to the version 2 OCX?" and I'd say "Yes please Mr. Gates" it would then fail to load the form. So, be prepared to use Notepad a lot.

- Andy.