Hi John,
Did you know that there is a newsgroup
microsoft.public.dotnet.languages.vb for vb.net you have the change that
they are saying to you to go to
microsoft.publicl.dotnet.languages.vb.upgrade
It is a very inactive newsgroup although Herfried K. Wagner is checks it
everyday.
He is mostly more willing to give answers about upgrading in the upgrading
newsgroup than in the language group because in his idea it has to be done
in the upgrade newsgroup.
As advice crosspost it to both.
I hope this helps?
Cor
I am attempting to upgrade a project written in VB6 that contains Excel
VBA code obtained by running macros, copying and pasting the code to VB6.
When this project is upgraded to .NET, the upgrade wizard defines an object
in an "UpgradeSupport.vb" module as Public ExcelGlobal_definst = New
Excel.Global. The problem is the object is not created, and does not work
in the code where the VBA code *did work*.
